SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
AIS-06: Automated Secure Application Deployment
Automated Secure Application Deployment
AIS-06: Are strategies and capabilities established and implemented to deploy application code in a secure, standardized, and compliant manner?
The strategies should include:
a. Defined security and automation requirements based on an organization's application deployment needs and standards.
b. Defined roles and responsibilities between security, application teams, and other stakeholder groups.
c. Identification and integration with existing application deployment processes.
d. Customization of secure application deployment for deployment types such as operating systems, network connections, configuration, etc.
e. Logging and monitoring of secure application deployment so that data issues can be promptly addressed by the appropriate people (incident or forensics).
f. Metrics to effectively measure deployment success.

The capabilities should be based on the organization's SSDLC and should include, for instance:
g. Defined and approved list of deployment and automation technologies.
h. Enablement for team members (e.g., developers, administrators, etc.) to dynamically address security issues when needed.

The strategies and capabilities should be reviewed periodically by senior management.
Control implemented
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.
Control ownership
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 and implement strategies and capabilities for secure, standardized, and compliant application deployment. Automate where possible.

Automated Secure Application Deployment
AIS-06: Is the deployment and integration of application code automated where possible?
The strategies should include:
a. Defined security and automation requirements based on an organization's application deployment needs and standards.
b. Defined roles and responsibilities between security, application teams, and other stakeholder groups.
c. Identification and integration with existing application deployment processes.
d. Customization of secure application deployment for deployment types such as operating systems, network connections, configuration, etc.
e. Logging and monitoring of secure application deployment so that data issues can be promptly addressed by the appropriate people (incident or forensics).
f. Metrics to effectively measure deployment success.

The capabilities should be based on the organization's SSDLC and should include, for instance:
g. Defined and approved list of deployment and automation technologies.
h. Enablement for team members (e.g., developers, administrators, etc.) to dynamically address security issues when needed.

The strategies and capabilities should be reviewed periodically by senior management.
Control implemented
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.
Control ownership
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 and implement strategies and capabilities for secure, standardized, and compliant application deployment. Automate where possible.