SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
TVM-01: Threat and Vulnerability Management Policy and Procedures
Threat and Vulnerability Management Policy and Procedures
TVM-01: Are policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained to identify, report, and prioritize the remediation of vulnerabilities to protect systems against vulnerability exploitation?
A policy on threat and vulnerability management (TVM) should be established that includes the intent, purpose, and governance of how a CSP or CSC must address threats and vulnerabilities for their respective scope under the SSRM.

At a minimum, the policy should specify:
a. What should be covered under the scope, especially the need to comply with applicable laws, regulations, and contractual requirements.
b. The frequency of assessments.
c. The methods that should be used.
d. How and when assessments and significant vulnerabilities should be reported, including when it’s appropriate to share vulnerability information with customers and business partners.
e. How reports should be reviewed.
f. How actions to address relevant risks and opportunities should be tracked to closure.
g. Approval of CSP native and (where applicable) third-party data/asset protection capabilities and relevant services for use by appropriate CSC authorities.
h. A well-defined incident response process aligned with an organization's risk tolerance, accompanied by appropriate communication and notifications.
i. Acceptable periods of remediation of threats in order of severity and criticality of computing infrastructure.
j. Log review and correlation procedures with appropriate threat intelligence capabilities for log, events, metrics, and incidents (preferably through a centralized service).
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, document, approve, communicate, apply, evaluate and maintain policies and procedures to identify, report and prioritize the remediation of vulnerabilities, in order to protect systems against vulnerability exploitation. Review and update the policies and procedures at least annually.

Threat and Vulnerability Management Policy and Procedures
TVM-01: Are threat and vulnerability management policies and procedures reviewed and updated at least annually?
A policy on threat and vulnerability management (TVM) should be established that includes the intent, purpose, and governance of how a CSP or CSC must address threats and vulnerabilities for their respective scope under the SSRM.

At a minimum, the policy should specify:
a. What should be covered under the scope, especially the need to comply with applicable laws, regulations, and contractual requirements.
b. The frequency of assessments.
c. The methods that should be used.
d. How and when assessments and significant vulnerabilities should be reported, including when it’s appropriate to share vulnerability information with customers and business partners.
e. How reports should be reviewed.
f. How actions to address relevant risks and opportunities should be tracked to closure.
g. Approval of CSP native and (where applicable) third-party data/asset protection capabilities and relevant services for use by appropriate CSC authorities.
h. A well-defined incident response process aligned with an organization's risk tolerance, accompanied by appropriate communication and notifications.
i. Acceptable periods of remediation of threats in order of severity and criticality of computing infrastructure.
j. Log review and correlation procedures with appropriate threat intelligence capabilities for log, events, metrics, and incidents (preferably through a centralized service).
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, document, approve, communicate, apply, evaluate and maintain policies and procedures to identify, report and prioritize the remediation of vulnerabilities, in order to protect systems against vulnerability exploitation. Review and update the policies and procedures at least annually.