Assessment Objectives
In addition to relevant policies, standards and procedures, the assessor shall examine, interview, and/or test to determine if appropriately scoped evidence exists to support the claim that:
- MON-09_A01 the content of audit records needed to support monitoring, analysis, investigation and reporting of unlawful or unauthorized system activity is defined.
Defined parameters: successful and unsuccessful account logon events, account management events, object access, policy change, privilege functions, process tracking, and system events. For Web applications: all administrator activity, authentication checks, authorization checks, data deletions, data access, data changes, and permission changes
Assessment rigor: 1
Origin: 171A_3.3.1[b] 171A_3.3.2[a] 53A_R5_AU-02_ODP[01] 53A_R5_AU-02_ODP[02] 53A_R5_AU-02a. 53A_R5_AU-02c.[01] - MON-09_A02 audit records contain information that establishes what type of event occurred.
Assessment rigor: 1
Origin: 53A_R5_AU-03a. 53A_R5_AU-02c.[02] - MON-09_A03 audit records contain information that establishes when the event occurred.
Assessment rigor: 1
Origin: 53A_R5_AU-03b. 53A_R5_AU-02c.[02] 171A_R3_A.03.03.02.a.02 - MON-09_A04 audit records contain information that establishes where the event occurred.
Assessment rigor: 1
Origin: 53A_R5_AU-03c. 53A_R5_AU-02c.[02] 171A_R3_A.03.03.02.a.03 - MON-09_A05 audit records contain information that establishes the source of the event.
Assessment rigor: 1
Origin: 53A_R5_AU-03d. 53A_R5_AU-02c.[02] 171A_R3_A.03.03.02.a.04 - MON-09_A06 audit records contain information that establishes the outcome of the event.
Assessment rigor: 1
Origin: 53A_R5_AU-03e. 53A_R5_AU-02c.[02] 171A_R3_A.03.03.02.a.05 - MON-09_A07 audit records contain information that establishes the identity of the individuals, subjects, objects, or entities associated with the event.
Assessment rigor: 1
Origin: 53A_R5_AU-03f. 171A_R3_A.03.03.02.a.06 - MON-09_A08 event logs needed (e.g., event types to be logged) to enable the monitoring, analysis, investigation and reporting of unlawful or unauthorized system activity are specified.
Assessment rigor: 2
Origin: 171A_3.3.1[a] - MON-09_A09 a rationale is provided for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents.
Assessment rigor: 3
Origin: 53A_R5_AU-02d. - MON-09_A10 audit records, once created, contain the defined content.
Assessment rigor: 2
Origin: 171A_3.3.1[d] 171A_3.3.2[b] - MON-09_A11 the frequency of event types selected for logging are reviewed / updated.
Defined parameters: at least weekly
Assessment rigor: 3
Origin: 53A_R5_AU-02_ODP[04] - MON-09_A12 event types selected for logging within the system are defined.
Assessment rigor: 2
Origin: 171A_R3_A.03.03.01.ODP[01] - MON-09_A13 the following event types are specified for logging within the system: <A.03.03.01.ODP[01]: event types>.
Defined parameters: SDP values: at a minimum and where applicable: (1) Authentication events: (a) Logons (Success/Failure) (b) Logoffs (Success) (2) Security Relevant File and Objects events: (a) Create (Success/Failure) (b) Access (Success/Failure) (c) Delete (Success/Failure) (d) Modify (Success/Failure) (e) Permission Modification (Success/Failure) (f) Ownership Modification (Success/Failure) (3) Export/Writes/downloads to devices/digital media (e.g., CD/DVD, USB, SD) (Success/Failure) (4) Import/Uploads from devices/digital media (e.g., CD/DVD, USB, SD) (Success/Failure) (5) User and Group Management events: (a) User add, delete, modify, disable, lock (Success/Failure) (b) Group/Role add, delete, modify (Success/Failure) 6) Use of Privileged/Special Rights events: (a) Security or audit policy changes (Success/Failure) (b) Configuration changes (Success/Failure) (7) Admin or root-level access (Success/Failure) (8) Privilege/Role escalation (Success/Failure) (9) Audit and security relevant log data accesses (Success/Failure) (10) System reboot, restart, and shutdown (Success/Failure) (11) Print to a device (Success/Failure) (12) Print to a file (e.g., pdf format) (Success/Failure) (13) Application (e.g., Adobe, Firefox, MS Office Suite) initialization (Success/Failure) For additional guidance, see: OMB21-31 ML 1
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.03.01.a - MON-09_A14 the event types selected for logging are updated <A.03.03.01.ODP[02]: frequency>.
Defined parameters: at least every 12 months and after any significant incidents or significant changes to risks
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.03.01.b[02] - MON-09_A15 additional information for audit records is provided, as needed.
Assessment rigor: 2
Origin: 171A_R3_A.03.03.02.b
Kwistjonijiet marbuta
| Tip ta’ link | Kwistjoni |
|---|---|
| blocks | Content of Event Logs |
- Secure Controls Framework -
The Secure Controls Framework® (SCF)
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.