Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
---|---|---|---|---|---|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1550 | Use Alternate Authentication Material |
Comments
This diagnostic statement provides secure application development, such as implementing token binding strategies to help prevent the malicious use of application access tokens.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1559 | Inter-Process Communication |
Comments
This diagnostic statement protects inter-process communication mechanisms from abuse through secure development practices, such as enabling the Hardened Runtime capability when developing applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1078 | Valid Accounts |
Comments
This diagnostic statement provides for secure system development, which includes ensuring that applications do not store sensitive data or valid account credentials insecurely (e.g., plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1078.002 | Domain Accounts |
Comments
This diagnostic statement provides for secure system development, which includes ensuring that applications do not store sensitive data or valid account credentials insecurely (e.g., plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1078.003 | Local Accounts |
Comments
This diagnostic statement provides for secure system development, which includes ensuring that applications do not store sensitive data or valid account credentials insecurely (e.g., plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1078.004 | Cloud Accounts |
Comments
This diagnostic statement provides for secure system development, which includes ensuring that applications do not store sensitive data or valid account credentials insecurely (e.g., plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1559 | Inter-Process Communication |
Comments
This diagnostic statement protects inter-process communication mechanisms from abuse through secure development practices, such as enabling the Hardened Runtime capability when developing applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1559.003 | XPC Services |
Comments
This diagnostic statement protects inter-process communication mechanisms from abuse through secure development practices, such as enabling the Hardened Runtime capability when developing applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1550 | Use Alternate Authentication Material |
Comments
This diagnostic statement provides for the implementation of secure development practices, such as implementing token binding strategies which can help prevent malicious use of application access tokens.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1550.001 | Application Access Token |
Comments
This diagnostic statement provides for the implementation of secure development practices, such as implementing token binding strategies which can help prevent malicious use of application access tokens.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1212 | Exploitation for Credential Access |
Comments
This diagnostic statement protects against Exploitation for Credential Access through the implementation of measures in the application to validate authentication requests by enabling one-time passwords, providing timestamps or sequence numbers for messages sent, using digital signatures, and/or using random session keys.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1564 | Hide Artifacts |
Comments
This diagnostic statement protects against Hide Artifacts through the implementation of application security processes and procedures such as installing applications to trusted system folder paths that are already protected by restricted file and directory permissions.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1564.009 | Resource Forking |
Comments
This diagnostic statement protects against Hide Artifacts through the implementation of application security processes and procedures such as installing applications to trusted system folder paths that are already protected by restricted file and directory permissions.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1564.012 | File/Path Exclusions |
Comments
This diagnostic statement protects against Hide Artifacts through the implementation of application security processes and procedures such as installing applications to trusted system folder paths that are already protected by restricted file and directory permissions.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1574 | Hijack Execution Flow |
Comments
This diagnostic statement provides for secure application development processes and procedures, such as including hash values in manifest files to help prevent side-loading of malicious libraries.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1574.002 | DLL Side-Loading |
Comments
This diagnostic statement provides for secure application development processes and procedures, such as including hash values in manifest files to help prevent side-loading of malicious libraries.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1559.003 | XPC Services |
Comments
This diagnostic statement protects inter-process communication mechanisms from abuse through secure development practices, such as enabling the Hardened Runtime capability when developing applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1647 | Plist File Modification |
Comments
This diagnostic statement helps protect the modification of property list files (plist files) through secure development practices, such as enabling hardened runtime.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1496.003 | SMS Pumping |
Comments
This diagnostic statement helps provides for secure development practices, such as implementing CAPTCHA protection on forms that send messages via SMS.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1593 | Search Open Websites/Domains |
Comments
This diagnostic statement provides for the use of secure development processes and procedures. This includes avoiding publishing sensitive information such as credentials and API keys when uploading to public code repositories.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1593.003 | Code Repositories |
Comments
This diagnostic statement provides for the use of secure development processes and procedures. This includes avoiding publishing sensitive information such as credentials and API keys when uploading to public code repositories.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1195 | Supply Chain Compromise |
Comments
This diagnostic statement provides for the use of secure development processes and procedures. This includes being cautious when selecting third-party libraries to integrate into applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1195.001 | Compromise Software Dependencies and Development Tools |
Comments
This diagnostic statement provides for the use of secure development processes and procedures. This includes being cautious when selecting third-party libraries to integrate into applications.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1550.001 | Application Access Token |
Comments
This diagnostic statement provides secure application development, such as implementing token binding strategies to help prevent the malicious use of application access tokens.
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1078.001 | Default Accounts |
Comments
This diagnostic statement provides for secure system development, which includes ensuring that applications do not store sensitive data or valid account credentials insecurely (e.g., plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).
|
PR.PS-06.01 | Secure SDLC process | Mitigates | T1195.001 | Compromise Software Dependencies and Development Tools |
Comments
This diagnostic statement provides for the use of secure development processes and procedures. This includes being cautious when selecting third-party libraries to integrate into applications.
|