MITRE ATT&CKmitigation
M1047 Audit
- Domain
- enterprise
- Version
- 1.3
- Created
- 2019-06-11
Description
Auditing is the process of recording activity and systematically reviewing and analyzing the activity and system configurations. The primary purpose of auditing is to detect anomalies and identify potential threats or weaknesses in the environment. Proper auditing configurations can also help to meet compliance requirements. The process of auditing encompasses regular analysis of user behaviors and system logs in support of proactive security measures.
Auditing is applicable to all systems used within an organization, from the front door of a building to accessing a file on a fileserver. It is considered more critical for regulated industries such as, healthcare, finance and government where compliance requirements demand stringent tracking of user and system activates.This mitigation can be implemented through the following measures:
System Audit:
• Use Case: Regularly assess system configurations to ensure compliance with organizational security policies.
• Implementation: Use tools to scan for deviations from established benchmarks.
Permission Audits:
• Use Case: Review file and folder permissions to minimize the risk of unauthorized access or privilege escalation.
• Implementation: Run access reviews to identify users or groups with excessive permissions.
Software Audits:
• Use Case: Identify outdated, unsupported, or insecure software that could serve as an attack vector.
• Implementation: Use inventory and vulnerability scanning tools to detect outdated versions and recommend secure alternatives.
Configuration Audits:
• Use Case: Evaluate system and network configurations to ensure secure settings (e.g., disabled SMBv1, enabled MFA).
• Implementation: Implement automated configuration scanning tools like SCAP (Security Content Automation Protocol) to identify non-compliant systems.
Network Audits:
• Use Case: Examine network traffic, firewall rules, and endpoint communications to identify unauthorized or insecure connections.
• Implementation: Utilize tools such as Wireshark, or Zeek to monitor and log suspicious network behavior.
Related
Mitigates · MITRE ATT&CK (111)
- T1685.007 Impair Autonomous Defenses sub-technique
- T1684 Social Engineering technique
- T1685 Disable or Modify Tools technique
- T1685.001 Disable or Modify Windows Event Log sub-technique
- T1685.004 Disable or Modify Linux Audit System Log sub-technique
- T1686 Disable or Modify System Firewall technique
- T1686.001 Cloud Firewall sub-technique
- T1686.002 Network Device Firewall sub-technique
- T1686.003 Windows Host Firewall sub-technique
- T1036.012 Browser Fingerprint sub-technique
- T1213.006 Databases sub-technique
- T1176.001 Browser Extensions sub-technique
- T1176.002 IDE Extensions sub-technique
- T1505.006 vSphere Installation Bundles sub-technique
- T1671 Cloud Application Integration technique
- T1666 Modify Cloud Resource Hierarchy technique
- T1558.005 Ccache Files sub-technique
- T1213.005 Messaging Applications sub-technique
- T1036.010 Masquerade Account Name sub-technique
- T1059.011 Lua sub-technique
- T1213.004 Customer Relationship Management Software sub-technique
- T1548.006 TCC Manipulation sub-technique
- T1578.005 Modify Cloud Compute Configurations sub-technique
- T1653 Power Settings technique
- T1556.008 Network Provider DLL sub-technique
- T1027.011 Fileless Storage sub-technique
- T1552.008 Chat Messages sub-technique
- T1556.007 Hybrid Identity sub-technique
- T1593.003 Code Repositories sub-technique
- T1649 Steal or Forge Authentication Certificates technique