List failing Drata monitoring tests
Automatically list failing Drata monitoring tests on drata.com. List the Drata monitoring tests that are currently failing in production, each with its failing resources or people: name, account, region and severity, plus how many findings and exclusions it has. Needs a Drata session. Read-only: it changes nothing in Drata.
Input
workspaceId optionalDrata workspace id. Defaults to the workspace the app opens.
includeFindings optionalAlso fetch the failing resources (findings) of each failing test.
Default: trueOutput
tests requiredfailingCount requiredcheckedAt optionalFAQ
Drata whoami (signed-in account)
Report which Drata account this browser is signed in as: the user id, email, name, roles, account type, and the workspace and region the app opened. When the browser is signed out, the run fails with a signed-out error asking you to sign in to Drata.
Retest a monitor (Drata)
Re-runs one Drata monitoring test right away (the "Test now" button) instead of waiting for the daily check, then waits for the new result and returns the status before and after, with the failing and excluded resource counts. Takes the test number shown in the Drata UI (e.g. 7 for "Only Authorized Employees Change Code"). Requires being signed in to Drata.
Update a Drata vendor
Changes fields of an existing vendor in Drata (Vendors, Current): status (e.g. bring an offboarded vendor back to Active), sub-processor and PII flags, trust center, website, privacy and terms links, services, stored data and risk levels. Only the fields you pass are changed. Takes the vendor number from its Drata page URL. Returns the vendor before and after. Requires being signed in to Drata.
