SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
DCS-01: Off-Site Equipment Disposal Policy and Procedures
Off-Site Equipment Disposal Policy and Procedures
DCS-01: Are policies and procedures for the secure disposal of equipment used outside the organization's premises established, documented, approved, communicated, enforced, and maintained?
When clients delete, leave, or egress a cloud platform, the provider should follow a sequence of structured steps to ensure that client data has been expunged from the provider environment according to the terms in the contract and best practice (per vetted guidance sources such as NIST 800-88). In addition, the client may request verification that data has been effectively removed.

These steps should include, but are not limited to:
a. Removal of sensitive data or systems not regularly accessed by the organization, service provider, partner, etc. (stand-alone systems).
b. Completion of a confidentiality assessment—including a verified process for select information sanitization and disposal processes.
c. A record of the process should be documented and communicated to support decisions.
d. All sanitized or destroyed assets should be logged into a tracking system with a certificate of media disposition (clear, purge, or destroy).
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 for the secure disposal of equipment used outside the organization's premises. If the equipment is not physically destroyed a data destruction procedure that renders recovery of information impossible must be applied. Review and update the policies and procedures at least annually.

Off-Site Equipment Disposal Policy and Procedures
DCS-01: Is a data destruction procedure applied that renders information recovery information impossible if equipment is not physically destroyed?
When clients delete, leave, or egress a cloud platform, the provider should follow a sequence of structured steps to ensure that client data has been expunged from the provider environment according to the terms in the contract and best practice (per vetted guidance sources such as NIST 800-88). In addition, the client may request verification that data has been effectively removed.

These steps should include, but are not limited to:
a. Removal of sensitive data or systems not regularly accessed by the organization, service provider, partner, etc. (stand-alone systems).
b. Completion of a confidentiality assessment—including a verified process for select information sanitization and disposal processes.
c. A record of the process should be documented and communicated to support decisions.
d. All sanitized or destroyed assets should be logged into a tracking system with a certificate of media disposition (clear, purge, or destroy).
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 for the secure disposal of equipment used outside the organization's premises. If the equipment is not physically destroyed a data destruction procedure that renders recovery of information impossible must be applied. Review and update the policies and procedures at least annually.

Off-Site Equipment Disposal Policy and Procedures
DCS-01: Are policies and procedures for the secure disposal of equipment used outside the organization's premises reviewed and updated at least annually?
When clients delete, leave, or egress a cloud platform, the provider should follow a sequence of structured steps to ensure that client data has been expunged from the provider environment according to the terms in the contract and best practice (per vetted guidance sources such as NIST 800-88). In addition, the client may request verification that data has been effectively removed.

These steps should include, but are not limited to:
a. Removal of sensitive data or systems not regularly accessed by the organization, service provider, partner, etc. (stand-alone systems).
b. Completion of a confidentiality assessment—including a verified process for select information sanitization and disposal processes.
c. A record of the process should be documented and communicated to support decisions.
d. All sanitized or destroyed assets should be logged into a tracking system with a certificate of media disposition (clear, purge, or destroy).
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 for the secure disposal of equipment used outside the organization's premises. If the equipment is not physically destroyed a data destruction procedure that renders recovery of information impossible must be applied. Review and update the policies and procedures at least annually.