1639
Nature Type ID Name Page
MemberOf 1009 Audit 2424
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 1210 Audit / Logging Errors 2475
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Technology : Cloud Computing (Prevalence = Undetermined)
Likelihood Of Exploit
Medium
Common Consequences
Scope Impact Likelihood
Non-Repudiation Hide Activities
If security critical information is not recorded, there will be
no trail for forensic analysis and discovering the cause
of problems or the source of attacks may become more
difficult or impossible.
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST),
can find some instances of this weakness by analyzing source code (or binary/compiled code)
without having to execute it. Typically, this is done by building a model of data flow and control
flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input)
with "sinks" (destinations where the data interacts with external components, a lower layer such
as the OS, etc.)
Effectiveness = High
Potential Mitigations
Phase: Architecture and Design
Use a centralized logging mechanism that supports multiple levels of detail.
Phase: Implementation
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.
Phase: Operation
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.
Phase: Operation
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.
Demonstrative Examples
CWE Version 4.14
CWE-778: Insufficient Logging
CWE-778: Insufficient Logging