CWE-778
Insufficient Logging
AI Translation Available
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
Status
draft
Abstraction
base
Likelihood
medium
Affected Platforms
Cloud Computing
Not Technology-Specific
Extended Description
AI Translation
When security-critical events are not logged properly, such as a failed login attempt, this can make malicious behavior more difficult to detect and may hinder forensic analysis after an attack succeeds.
As organizations adopt cloud storage resources, these technologies often require configuration changes to enable detailed logging information, since detailed logging can incur additional costs. This could lead to telemetry gaps in critical audit logs. For example, in Azure, the default value for logging is disabled.
Technical Details
AI Translation
Common Consequences
non-repudiation
Impacts
hide activities
Detection Methods
automated static analysis
Potential Mitigations
Phases:
architecture and design
implementation
operation
Descriptions:
•
Use a centralized logging mechanism that supports multiple levels of detail.
•
Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.
•
To enable storage logging using Azure's Portal, navigate to the name of the Storage Account, locate Monitoring (CLASSIC) section, and select Diagnostic settings (classic). For each of the various properties (blob, file, table, queue), ensure the status is properly set for the desired logging data. If using PowerShell, the Set-AzStorageServiceLoggingProperty command could be called using appropriate -ServiceType, -LoggingOperations, and -RetentionDays arguments.
•
Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks. At the same time, logging too much data (CWE-779) can cause the same problems, including unexpected costs when using a cloud environment.