compliance controls are associated with this Policy definition 'Configure Azure Audit capabilities' (a3e98638-51d4-4e28-910a-60e98c1a756f)
| Control Domain |
Control |
Name |
MetadataId |
Category |
Title |
Owner |
Requirements |
Description |
Info |
Policy# |
| CIS_Azure_1.1.0 |
3.3 |
CIS_Azure_1.1.0_3.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.3 |
3 Storage Accounts |
Ensure Storage logging is enabled for Queue service for read, write, and delete requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.3.0 |
3.10 |
CIS_Azure_1.3.0_3.10 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.10 |
3 Storage Accounts |
Ensure Storage logging is enabled for Blob service for read, write, and delete requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.3.0 |
3.11 |
CIS_Azure_1.3.0_3.11 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.11 |
3 Storage Accounts |
Ensure Storage logging is enabled for Table service for read, write, and delete requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Table storage is a service that stores structure NoSQL data in the cloud, providing a key/attribute store with a schema less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.3.0 |
3.3 |
CIS_Azure_1.3.0_3.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.3 |
3 Storage Accounts |
Ensure Storage logging is enabled for Queue service for read, write, and delete requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.3.0 |
5.1.2 |
CIS_Azure_1.3.0_5.1.2 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 |
5 Logging and Monitoring |
Ensure Diagnostic Setting captures appropriate categories |
Shared |
The customer is responsible for implementing this recommendation. |
The diagnostic setting should be configured to log the appropriate activities from the control/management plane. |
link |
5 |
| CIS_Azure_1.3.0 |
5.3 |
CIS_Azure_1.3.0_5.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.3 |
5 Logging and Monitoring |
Ensure that Diagnostic Logs are enabled for all services which support it. |
Shared |
The customer is responsible for implementing this recommendation. |
Diagnostic Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself, for example, getting a secret from a Key Vault. Currently, 32 Azure resources support Diagnostic Logging (See the references section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps and CosmosDB. The content of these logs varies by resource type. For example, Windows event system logs are a category of diagnostics logs
for VMs, and blob, table, and queue logs are categories of diagnostics logs for storage accounts.
A number of back-end services were not configured to log and store Diagnostic Logs for certain activities or for a sufficient length. It is crucial that logging systems are correctly configured to log all relevant activities and retain those logs for a sufficient length of time. By default, Diagnostic Logs are not enabled. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended.
Note: The CIS Benchmark covers some specific Diagnostic Logs
separately.
'''
3.3 - Ensure Storage logging is enabled for Queue service for read, write, and delete requests
6.4 Ensure that Network Security Group Flow Log retention period is 'greater than 90 days'
''' |
link |
20 |
| CIS_Azure_1.4.0 |
3.10 |
CIS_Azure_1.4.0_3.10 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.10 |
3 Storage Accounts |
Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.4.0 |
3.11 |
CIS_Azure_1.4.0_3.11 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.11 |
3 Storage Accounts |
Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Table storage is a service that stores structure NoSQL data in the cloud, providing a key/attribute store with a schema less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.4.0 |
3.3 |
CIS_Azure_1.4.0_3.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.3 |
3 Storage Accounts |
Ensure Storage Logging is Enabled for Queue Service for 'Read', 'Write', and 'Delete' requests |
Shared |
The customer is responsible for implementing this recommendation. |
The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. |
link |
5 |
| CIS_Azure_1.4.0 |
5.1.2 |
CIS_Azure_1.4.0_5.1.2 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 |
5 Logging and Monitoring |
Ensure Diagnostic Setting captures appropriate categories |
Shared |
The customer is responsible for implementing this recommendation. |
The diagnostic setting should be configured to log the appropriate activities from the control/management plane. |
link |
5 |
| CIS_Azure_1.4.0 |
5.3 |
CIS_Azure_1.4.0_5.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.3 |
5 Logging and Monitoring |
Ensure that Diagnostic Logs Are Enabled for All Services that Support it. |
Shared |
The customer is responsible for implementing this recommendation. |
Diagnostic Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself, for example, getting a secret from a Key Vault. Currently, 32 Azure resources support Diagnostic Logging (See the references section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps and CosmosDB. The content of these logs varies by resource type. For example, Windows event system logs are a category of diagnostics logs
for VMs, and blob, table, and queue logs are categories of diagnostics logs for storage accounts.
A number of back-end services were not configured to log and store Diagnostic Logs for certain activities or for a sufficient length. It is crucial that logging systems are correctly configured to log all relevant activities and retain those logs for a sufficient length of time. By default, Diagnostic Logs are not enabled. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended.
Note: The CIS Benchmark covers some specific Diagnostic Logs
separately.
'''
3.3 - Ensure Storage logging is enabled for Queue service for read, write, and delete requests
6.4 Ensure that Network Security Group Flow Log retention period is 'greater than 90 days'
''' |
link |
20 |
| CIS_Azure_2.0.0 |
3.13 |
CIS_Azure_2.0.0_3.13 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.13 |
3 |
Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests |
Shared |
Being a level 2, enabling this setting can have a high impact on the cost of data storage used for logging more data per each request. Do not enable this without determining your need for this level of logging or forget to check in on data usage and projected cost. |
The Storage Blob service provides scalable, cost-efficient object storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: timing information such as start time, end-to-end latency, and server latency; authentication details; concurrency information; and the sizes of the request and response messages.
Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor each individual request to a storage service for increased security or diagnostics. Requests are logged on a best-effort basis.
Storage Analytics logging is not enabled by default for your storage account. |
link |
5 |
| CIS_Azure_2.0.0 |
3.14 |
CIS_Azure_2.0.0_3.14 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.14 |
3 |
Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests |
Shared |
Being a level 2, enabling this setting can have a high impact on the cost of data storage used for logging more data per each request. Do not enable this without determining your need for this level of logging or forget to check in on data usage and projected cost. |
Azure Table storage is a service that stores structured NoSQL data in the cloud, providing a key/attribute store with a schema-less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: timing information such as start time, end-to-end latency, and server latency; authentication details; concurrency information; and the sizes of the request and response messages.
Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor each individual request to a storage service for increased security or diagnostics. Requests are logged on a best-effort basis.
Storage Analytics logging is not enabled by default for your storage account. |
link |
5 |
| CIS_Azure_2.0.0 |
3.5 |
CIS_Azure_2.0.0_3.5 |
CIS Microsoft Azure Foundations Benchmark recommendation 3.5 |
3 |
Ensure Storage Logging is Enabled for Queue Service for 'Read', 'Write', and 'Delete' requests |
Shared |
Enabling this setting can have a high impact on the cost of the log analytics service and data storage used by logging more data per each request. Do not enable this without determining your need for this level of logging, and do not forget to check in on data usage and projected cost. Some users have seen their logging costs increase from $10 per month to $10,000 per month. |
The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details, concurrency information, and the sizes of the request and response messages.
Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis.
Storage Analytics logging is not enabled by default for your storage account. |
link |
5 |
| CIS_Azure_2.0.0 |
5.1.2 |
CIS_Azure_2.0.0_5.1.2 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 |
5.1 |
Ensure Diagnostic Setting captures appropriate categories |
Shared |
n/a |
**Prerequisite**: A Diagnostic Setting must exist. If a Diagnostic Setting does not exist, the navigation and options within this recommendation will not be available. Please review the recommendation at the beginning of this subsection titled: "Ensure that a 'Diagnostic Setting' exists."
The diagnostic setting should be configured to log the appropriate activities from the control/management plane.
A diagnostic setting controls how the diagnostic log is exported. Capturing the diagnostic setting categories for appropriate control/management plane activities allows proper alerting. |
link |
8 |
| CIS_Azure_2.0.0 |
5.4 |
CIS_Azure_2.0.0_5.4 |
CIS Microsoft Azure Foundations Benchmark recommendation 5.4 |
5 |
Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it |
Shared |
Costs for monitoring varies with Log Volume. Not every resource needs to have logging enabled. It is important to determine the security classification of the data being processed by the given resource and adjust the logging based on which events need to be tracked. This is typically determined by governance and compliance requirements. |
Resource Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself; for example, reading or updating a secret from a Key Vault. Currently, 95 Azure resources support Azure Monitoring (See the more information section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps, and CosmosDB. The content of these logs varies by resource type.
A number of back-end services were not configured to log and store Resource Logs for certain activities or for a sufficient length. It is crucial that monitoring is correctly configured to log all relevant activities and retain those logs for a sufficient length of time. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended.
A lack of monitoring reduces the visibility into the data plane, and therefore an organization's ability to detect reconnaissance, authorization attempts or other malicious activity. Unlike Activity Logs, Resource Logs are not enabled by default. Specifically, without monitoring it would be impossible to tell which entities had accessed a data store that was breached. In addition, alerts for failed attempts to access APIs for Web Services or Databases are only possible when logging is enabled. |
link |
20 |
| FedRAMP_High_R4 |
AU-3(1) |
FedRAMP_High_R4_AU-3(1) |
FedRAMP High AU-3 (1) |
Audit And Accountability |
Additional Audit Information |
Shared |
n/a |
The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information].
Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. |
link |
1 |
| FedRAMP_Moderate_R4 |
AU-3(1) |
FedRAMP_Moderate_R4_AU-3(1) |
FedRAMP Moderate AU-3 (1) |
Audit And Accountability |
Additional Audit Information |
Shared |
n/a |
The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information].
Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. |
link |
1 |
| hipaa |
1202.09aa1System.1-09.aa |
hipaa-1202.09aa1System.1-09.aa |
1202.09aa1System.1-09.aa |
12 Audit Logging & Monitoring |
1202.09aa1System.1-09.aa 09.10 Monitoring |
Shared |
n/a |
A secure audit record is created for all activities on the system (create, read, update, delete) involving covered information. |
|
4 |
| hipaa |
1203.09aa1System.2-09.aa |
hipaa-1203.09aa1System.2-09.aa |
1203.09aa1System.2-09.aa |
12 Audit Logging & Monitoring |
1203.09aa1System.2-09.aa 09.10 Monitoring |
Shared |
n/a |
Audit records include the unique user ID, unique data subject ID, function performed, and date/time the event was performed. |
|
3 |
| hipaa |
1204.09aa1System.3-09.aa |
hipaa-1204.09aa1System.3-09.aa |
1204.09aa1System.3-09.aa |
12 Audit Logging & Monitoring |
1204.09aa1System.3-09.aa 09.10 Monitoring |
Shared |
n/a |
The activities of privileged users (administrators, operators, etc.) include the success/failure of the event, time the event occurred, the account involved, the processes involved, and additional information about the event. |
|
4 |
| hipaa |
1205.09aa2System.1-09.aa |
hipaa-1205.09aa2System.1-09.aa |
1205.09aa2System.1-09.aa |
12 Audit Logging & Monitoring |
1205.09aa2System.1-09.aa 09.10 Monitoring |
Shared |
n/a |
Logs of messages sent and received are maintained including the date, time, origin and destination of the message, but not its contents. |
|
6 |
| hipaa |
1206.09aa2System.23-09.aa |
hipaa-1206.09aa2System.23-09.aa |
1206.09aa2System.23-09.aa |
12 Audit Logging & Monitoring |
1206.09aa2System.23-09.aa 09.10 Monitoring |
Shared |
n/a |
Auditing is always available while the system is active and tracks key events, success/failed data access, system security configuration changes, privileged or utility use, any alarms raised, activation and de-activation of protection systems (e.g., A/V and IDS), activation and deactivation of identification and authentication mechanisms, and creation and deletion of system-level objects. |
|
6 |
| hipaa |
1207.09aa2System.4-09.aa |
hipaa-1207.09aa2System.4-09.aa |
1207.09aa2System.4-09.aa |
12 Audit Logging & Monitoring |
1207.09aa2System.4-09.aa 09.10 Monitoring |
Shared |
n/a |
Audit records are retained for 90 days and older audit records are archived for one year. |
|
13 |
| hipaa |
1208.09aa3System.1-09.aa |
hipaa-1208.09aa3System.1-09.aa |
1208.09aa3System.1-09.aa |
12 Audit Logging & Monitoring |
1208.09aa3System.1-09.aa 09.10 Monitoring |
Shared |
n/a |
Audit logs are maintained for management activities, system and application startup/shutdown/errors, file changes, and security policy changes. |
|
18 |
| hipaa |
1209.09aa3System.2-09.aa |
hipaa-1209.09aa3System.2-09.aa |
1209.09aa3System.2-09.aa |
12 Audit Logging & Monitoring |
1209.09aa3System.2-09.aa 09.10 Monitoring |
Shared |
n/a |
The information system generates audit records containing the following detailed information: (i) filename accessed; (ii) program or command used to initiate the event; and, (iii) source and destination addresses. |
|
3 |
| hipaa |
1214.09ab2System.3456-09.ab |
hipaa-1214.09ab2System.3456-09.ab |
1214.09ab2System.3456-09.ab |
12 Audit Logging & Monitoring |
1214.09ab2System.3456-09.ab 09.10 Monitoring |
Shared |
n/a |
Monitoring includes privileged operations, authorized access or unauthorized access attempts, including attempts to access deactivated accounts, and system alerts or failures. |
|
9 |
| hipaa |
1216.09ab3System.12-09.ab |
hipaa-1216.09ab3System.12-09.ab |
1216.09ab3System.12-09.ab |
12 Audit Logging & Monitoring |
1216.09ab3System.12-09.ab 09.10 Monitoring |
Shared |
n/a |
Automated systems are used to review monitoring activities of security systems (e.g., IPS/IDS) and system records on a daily basis, and identify and document anomalies. |
|
20 |
| hipaa |
1230.09c2Organizational.1-09.c |
hipaa-1230.09c2Organizational.1-09.c |
1230.09c2Organizational.1-09.c |
12 Audit Logging & Monitoring |
1230.09c2Organizational.1-09.c 09.01 Documented Operating Procedures |
Shared |
n/a |
No single person is able to access, modify, or use information systems without authorization or detection. |
|
13 |
| ISO27001-2013 |
A.12.4.1 |
ISO27001-2013_A.12.4.1 |
ISO 27001:2013 A.12.4.1 |
Operations Security |
Event Logging |
Shared |
n/a |
Event logs recording user activities, exceptions, faults and information security events shall be produced, kept and regularly reviewed. |
link |
53 |
| NIST_SP_800-171_R2_3 |
.3.1 |
NIST_SP_800-171_R2_3.3.1 |
NIST SP 800-171 R2 3.3.1 |
Audit and Accountability |
Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity |
Shared |
Microsoft and the customer share responsibilities for implementing this requirement. |
An event is any observable occurrence in a system, which includes unlawful or unauthorized system activity. Organizations identify event types for which a logging functionality is needed as those events which are significant and relevant to the security of systems and the environments in which those systems operate to meet specific and ongoing auditing needs. Event types can include password changes, failed logons or failed accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the monitoring and auditing appropriate for each of the CUI security requirements. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of event types, the logging necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloud-based architectures. Audit record content that may be necessary to satisfy this requirement includes time stamps, source and destination addresses, user or process identifiers, event descriptions, success or fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations may consider in audit records includes full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit log information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. Audit logs are reviewed and analyzed as often as needed to provide important information to organizations to facilitate risk-based decision making. [SP 800-92] provides guidance on security log management. |
link |
50 |
| NIST_SP_800-53_R4 |
AU-3(1) |
NIST_SP_800-53_R4_AU-3(1) |
NIST SP 800-53 Rev. 4 AU-3 (1) |
Audit And Accountability |
Additional Audit Information |
Shared |
n/a |
The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information].
Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. |
link |
1 |
| NIST_SP_800-53_R5 |
AU-3(1) |
NIST_SP_800-53_R5_AU-3(1) |
NIST SP 800-53 Rev. 5 AU-3 (1) |
Audit and Accountability |
Additional Audit Information |
Shared |
n/a |
Generate audit records containing the following additional information: [Assignment: organization-defined additional information]. |
link |
1 |
|
op.exp.8 Recording of the activity |
op.exp.8 Recording of the activity |
404 not found |
|
|
|
n/a |
n/a |
|
67 |