601
According to SOAR, the following detection techniques may be useful: Highly cost effective:
Manual Source Code Review (not inspections) Cost effective for partial coverage: Focused
Manual Spotcheck - Focused manual analysis of source
Effectiveness = High
Automated Static Analysis - Source Code
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Source code Weakness Analyzer Context-configured Source Code Weakness
Analyzer
Effectiveness = SOAR Partial
Automated Static Analysis
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Configuration Checker Permission Manifest Analysis
Effectiveness = SOAR Partial
Architecture or Design Review
According to SOAR, the following detection techniques may be useful: Highly cost effective:
Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.) Formal
Methods / Correct-By-Construction Cost effective for partial coverage: Attack Modeling
Effectiveness = High
Potential Mitigations
Phase: Architecture and Design
Phase: Operation
Strategy = Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks
[REF-76]. If possible, create isolated accounts with limited privileges that are only used for a
single task. That way, a successful attack will not immediately give the attacker access to the
rest of the software or its environment. For example, database applications rarely need to run as
the database administrator, especially in day-to-day operations.
Phase: Architecture and Design
Strategy = Separation of Privilege
Identify the functionality that requires additional privileges, such as access to privileged
operating system resources. Wrap and centralize this functionality if possible, and isolate the
privileged code as much as possible from other code [REF-76]. Raise privileges as late as
possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as
CWE-288 and CWE-420 by protecting all possible communication channels that could interact
with the privileged code, such as a secondary socket that is only intended to be accessed by
administrators.
Phase: Architecture and Design
Strategy = Attack Surface Reduction
Identify the functionality that requires additional privileges, such as access to privileged
operating system resources. Wrap and centralize this functionality if possible, and isolate the
privileged code as much as possible from other code [REF-76]. Raise privileges as late as
possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as
CWE-288 and CWE-420 by protecting all possible communication channels that could interact
with the privileged code, such as a secondary socket that is only intended to be accessed by
administrators.
Phase: Implementation
CWE Version 4.14
CWE-250: Execution with Unnecessary Privileges
CWE-250: Execution with Unnecessary Privileges