App Logo
drata.com

Drata compliance status: failing tests, controls and personnel

Get everything currently failing in your Drata workspace in one call: the monitoring tests in failure with the date they started failing, the number of days since and the failing resources; the in-scope controls that are not ready with what they are missing; and the current personnel who are not compliant with the checks they fail. Needs a Drata session. Read-only: it changes nothing in Drata.

Input

sections optional

Which lists to return. Defaults to all three.

workspaceId optional

Drata workspace id. Defaults to the workspace the app opens.

Output

summary required
checkedAt required
workspaceId required
failingTests optional
notReadyControls optional
personnelInScope optional
nonCompliantPersonnel optional

FAQ

Get everything currently failing in your Drata workspace in one call: the monitoring tests in failure with the date they started failing, the number of days since and the failing resources; the in-scope controls that are not ready with what they are missing; and the current personnel who are not compliant with the checks they fail. Needs a Drata session. Read-only: it changes nothing in Drata.
Optional: sections, workspaceId.
It returns summary, checkedAt, workspaceId, failingTests, notReadyControls, personnelInScope, nonCompliantPersonnel.
Yes. It acts as you on drata.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the drata.com cookies saved by the Reduck extension.
It only reads. It looks things up on drata.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/drata.com/compliance_status, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/drata.com/compliance_status
It is part of Reduck's official curated catalogue.

Related scripts

drata.com

Drata whoami (signed-in account)

Report which Drata account this browser is signed in as: the user id, email, first and last name, roles, account type, and the workspace and region the app opened. Being signed out is reported as a normal answer (loggedIn false), not an error, so it can be used to check a session before running other Drata scripts.

app.drata.com

Exclude a Drata monitoring finding

Exclude one failing resource (a repository, a person, a cloud resource) from a Drata monitoring test, with the written justification Drata shows auditors in its audit packages. Give the test page URL, the resource exactly as listed in the test's findings, and the reason. Needs a Drata session. It changes your compliance results, and undoing it is done from the test's Exclusions tab.

drata.com

Drata: list my policies

List the Drata policies assigned to the signed-in employee, with each policy's name, description, published date and whether (and when) the employee accepted it, plus totals. Read-only; it never accepts a policy.

Start building not clicking

Get started for free