Source

Controls, SoA & measures — found from sitemap — Drata

Checked for Drata on 13 Oct 2026

Page: https://help.drata.com/en/articles/13381764-mark-controls-in-or-out-of-scope
Checked: 13 Oct 2026, 12:59 UTC
How we may use it: Public page, crawling permitted

Technical details

type: page
http status: 200
content hash: sha256:c0b74d90ceeb7c07f0a352de862135caeb4daf5dbc9c485505bb892756e14f86
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Control scope marking Report an error

“Drata allows you to mark controls as In Scope or Out of Scope so your audit reflects only the controls your organization plans to use.”
Scope roles restricted Report an error

“Only the following roles can mark controls in or out of scope: Administrators Information Security Leads”
Scope global Report an error

“Control scope is global. When you mark a control In/Out of Scope from the Controls page, it affects all frameworks that control is mapped to”
Out of scope excluded from readiness Report an error

“The selected controls are excluded from audit scope and readiness calculations where applicable.”
Framework readiness based on inscope mappings Report an error

“A framework’s control count and readiness are based on in‑scope controls that are mapped to in‑scope requirements in that framework.”
Bulk control selection Report an error

“Use the tick box next to a control or group of controls (you can select multiple or all on the page), then click the file box icon on the far right of the screen to mark the controls 'Out of Scope'.”
Interface versions Report an error

“The steps to mark controls in or out of scope vary depending on your interface version.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.