15.7 Securely Decommission Service Providers
Decommission service providers securely, considering steps such as deactivating user and service accounts, ending data flows and securely disposing of enterprise data held in the provider's systems. Implementation Group: IG3 only (for enterprises facing sophisticated attackers or holding highly sensitive data). Asset type: Data. Security function: Protect.
Source: CIS Controls v8.1, 15.7. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Account deactivation and data flow termination records · Identity provider / directory
periodic reviewEvidence produced at each review
- Provider confirmation or certificate of data deletion · Vendor register / contract repository
governing documentDocuments that govern the control
- Provider offboarding checklist · HR system / LMS
First move
Common gaps auditors find
- Integration credentials left active
- No proof of data deletion
- Data flows still running after exit
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet15.6 Monitor Service Providers · 16.1 Establish and Maintain a Secure Application Development Process