SAMMY works best on screens 1024px wide or larger.
Cloud Controls Matrix
Browse Cloud Controls...
AIS-01: Application and Interface Security Policy and Procedures
Application and Interface Security Policy and Procedures
AIS-01: Are application security policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained to guide appropriate planning, delivery, and support of the organization's application security capabilities?

The policy should:


a. Include defined roles and responsibilities supported by regular workforce training.
b. Align with organizational purpose and strategy.
c. Provide a framework for setting application security baselines (e.g., NIST, ISO, OWASP, and CIS benchmarks).
d. Guide the development of application security controls.
e. Include a commitment to satisfy applicable requirements and continual improvement.
f. Cover all relevant applications regardless of whether they are developed in-house or via one’s supply chain.
g. Promote the use of an established software development lifecycle (SDLC) in software development, including code review, secure coding training, testing (functional, regression, security, etc.), vulnerability testing, and change management.
h. Ensure vulnerability processes are followed with regular patching, scanning, and remediation before production deployment.
i. Be reviewed by management periodically or after significant changes.


Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for application security to provide guidance to the appropriate planning, delivery and support of the organization's application security capabilities. Review and update the policies and procedures at least annually.

Application and Interface Security Policy and Procedures
AIS-01: Are application security policies and procedures reviewed and updated at least annually?

The policy should:


a. Include defined roles and responsibilities supported by regular workforce training.
b. Align with organizational purpose and strategy.
c. Provide a framework for setting application security baselines (e.g., NIST, ISO, OWASP, and CIS benchmarks).
d. Guide the development of application security controls.
e. Include a commitment to satisfy applicable requirements and continual improvement.
f. Cover all relevant applications regardless of whether they are developed in-house or via one’s supply chain.
g. Promote the use of an established software development lifecycle (SDLC) in software development, including code review, secure coding training, testing (functional, regression, security, etc.), vulnerability testing, and change management.
h. Ensure vulnerability processes are followed with regular patching, scanning, and remediation before production deployment.
i. Be reviewed by management periodically or after significant changes.


Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for application security to provide guidance to the appropriate planning, delivery and support of the organization's application security capabilities. Review and update the policies and procedures at least annually.