Tracecat
Book a demo
Protect
PR.DS

Automate data protection checks

Find encryption gaps, collect context for data-loss alerts, and follow up failed backup jobs. Record findings with the affected resource and an owner so each gap has a next step.

Tools for data security

MCP servers for the tools used in these examples.

Automation examples and starter prompts

Paste a prompt into Claude Code, Microsoft Copilot, or Codex connected to Tracecat MCP. Adapt it to your tools and test before deployment. Human tool approvals and advanced case features require Enterprise.

Audit encryption at rest in the cloud

Build me an encryption audit automation in Tracecat. Every morning, pull Wiz findings for unencrypted S3 buckets, EBS volumes, and RDS instances, then check each one against AWS to confirm it still exists and who owns it. Record every gap in a Tracecat table, open a Jira ticket per resource owner, and close tickets automatically once the resource shows up encrypted. First help me understand how this maps to PR.DS-01 and what good data-at-rest protection looks like beyond turning on default encryption. Ask me which AWS accounts are in scope and which Jira project to file against. Talk me through whether the auto-close logic can run unattended or needs an approval gate.

Verify disk encryption on laptops

Build me an endpoint encryption check in Tracecat. Pull the device inventory from Jamf each week and flag any Mac without FileVault enabled or with no recovery key escrowed, then cross-check the Windows fleet in Microsoft Defender XDR for BitLocker status. Open a case per unencrypted device, email the device owner with a remediation deadline, and follow up automatically if nothing changes in seven days. First help me understand how this maps to PR.DS-01 and why full disk encryption on user endpoints is the control auditors check first. Ask me whether my fleet is Jamf-only or split with Windows, and where escrowed recovery keys live. Talk me through how many reminder cycles to run before a device escalates to IT leadership.

Triage data leaving the network

Build me a DLP triage automation in Tracecat. Receive Zscaler DLP alerts over a webhook and open a case for each one. When the case opens, run an AI agent that enriches the user from Okta with their team, manager, and recent sign-in activity. If the destination is a personal email or file sharing service, raise the case severity, block follow-on uploads for that user in Zscaler, and notify the security channel in Microsoft Teams with the file name, classification, and destination. First help me understand how this maps to PR.DS-02 and what protecting data in transit means in practice beyond TLS. Ask me which data classifications should trigger a block versus a notify-only response. Talk me through whether the Zscaler block should be automatic or sit behind an approval step in the case.

Track backup jobs and restore tests

Build me a backup assurance automation in Tracecat. Pull AWS Backup job results every morning and record failures in a Tracecat table with the resource, vault, and error. Open a ServiceNow incident for any critical system whose backups have failed two days running. Once a quarter, run a scheduled workflow that picks a sample of backups, files a restore test task in ServiceNow for each system owner, and chases the results until each test is logged as passed or failed. First help me understand how this maps to PR.DS-11 and why tested restores matter more than backup success rates. Ask me which systems count as critical and how often each tier should be backed up. Talk me through choosing the failure threshold that pages someone versus the one that just files a ticket.

NIST CSF 2.0 mapping: PR.DS

Official NIST category: Data Security. Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information

The controls and implementation examples below are NIST source material. The automation prompts above are Tracecat-authored starting points, not evidence of compliance or full control coverage.

  • PR.DS-01
    CA-3
    CP-9
    MP-8
    SC-4
    SC-7
    SC-12
    SC-13
    SC-28
    SC-32
    SC-39
    SC-43
    SI-3
    SI-4
    SI-7

    The confidentiality, integrity, and availability of data-at-rest are protected

  • PR.DS-02
    AU-16
    CA-3
    SC-4
    SC-7
    SC-8
    SC-11
    SC-12
    SC-13
    SC-16
    SC-40
    SC-43
    SI-3
    SI-4
    SI-7

    The confidentiality, integrity, and availability of data-in-transit are protected

  • PR.DS-10
    AC-2
    AC-3
    AC-4
    AU-9
    AU-13
    CA-3
    CP-9
    SA-8
    SC-4
    SC-7
    SC-11
    SC-13
    SC-24
    SC-32
    SC-39
    SC-40
    SC-43
    SI-3
    SI-4
    SI-7
    SI-10
    SI-16

    The confidentiality, integrity, and availability of data-in-use are protected

  • PR.DS-11
    CP-6
    CP-9

    Backups of data are created, protected, maintained, and tested

Control text and SP 800-53 Rev 5 references from the official NIST CSF 2.0 and OLIR releases.

Build your own security automation

Adapt a starter prompt with your coding assistant, choose where AI agents or fixed workflows fit, and test with your tools.