Skip to main content
A playbook is a ready-made set of compliance checks. This guide shows MSP staff how to go from choosing a playbook to running an assessment. Company users see the finished assessments their IT provider shares. They do not import playbooks.

​
Before you start

  • You need read_settings_playbooks to browse and manage_settings_playbooks plus an active billing account to import.
  • Your tenant needs at least one status list. The import asks you to choose one.
  • Importing copies checks into your tenant. It does not change any endpoint, start an assessment or assign checks to a company.

​
From playbook to assessment

1

Open the Playbooks library

Go to Settings > Compliance > Playbooks. Click Best Practices for broad operational and technology reviews, or Security Frameworks for framework families such as CIS Benchmarks, CAN/DGSI 104, NIS2, NIST CSF 2.0 and Cyber Essentials. Or type in Search all playbooks….
The Playbooks home page with the Best Practices and Security Frameworks cards

The Playbooks home page with the Best Practices and Security Frameworks cards.

2

Read the checks

Click the playbook’s name to open its details. The window is read-only. Click Cancel to close it. Check the card’s version and check count.
3

Import the playbook

Click Add on the card. In Add Playbooks to Tenant, check the folder, choose a Status list, review the Device types if shown, then click Add to Tenant. A card marked Imported was imported before; importing it again adds only missing checks to the existing group. See Playbook settings for every dialog option.
4

Tune the imported checks

Open Settings > Compliance > Checks and find the folder named in the import message. Edit the guidance and which companies and devices each check applies to. See Compliance settings.
5

Put the group in a run template

Open Settings > Compliance > Runs. Create a template, or open one, then add the imported group on its Groups tab.
6

Run the assessment

Run the template against the companies you choose, collect evidence and review the results in Compliance.
A playbook standardizes the questions you ask every client. It does not supply evidence or certify a client. Check the product version and the client’s scope before you assign a benchmark.

​
Keep imported content current

Importing a playbook again adds checks that are missing from your copy, such as checks added to the catalog since your first import, to the existing group. It does not update checks you already have, so review edited checks against the catalog yourself. The Imported badge shows that the tenant already holds checks from that playbook. For CIS product families and L1 or L2 profiles, see Adding CIS Benchmarks. CIS benchmark profiles are different from CIS Controls Implementation Groups. For clients under the EU NIS2 directive, see Adding NIS2 playbooks.

​
Troubleshooting

​
Frequently asked questions

No. It is check content. You still run the assessment and record evidence.
No. Importing is an MSP settings task.
No. It adds checks and a group to your tenant. Fixing a client’s configuration is separate work.
Use the catalog your account shows, with its names, versions and check counts.
No. Add it to a run template and run it for the companies you choose.