Reversibility of managed DLP

The managed DLP (Data Loss Prevention) service is designed to guarantee reversibility, meaning the ability for the customer to recover their data and migrate to another solution without vendor lock-in.

Exportable data

All DLP service data can be exported via the Control API:

• rules and their version history;
• policies and their version history;
• custom detectors;
• decision logs;
• monitored events;
• the audit trail.

Reversibility tools

Export via the Control API

Use the Control API to export configurations:

# Export rules
curl -b dlp_session=<cookie> /api/v1/rules > rules.json

# Export policies
curl -b dlp_session=<cookie> /api/v1/policies > policies.json

# Export custom detectors
curl -b dlp_session=<cookie> /api/v1/detectors/custom > custom-detectors.json

# Export decision logs
curl -b dlp_session=<cookie> "/api/v1/logs/decisions?time_start=2020-01-01T00:00:00Z" > decisions.json

Export of published rulesets

Each published version of the ruleset can be retrieved via the API:

curl -b dlp_session=<cookie> /api/v1/rulesets/{version} > ruleset-v{version}.json

Open formats

• Rules and policies are in JSON format, an industry standard;
• Detectors use RE2-compatible regular expressions;
• Decision logs are in JSON format;
• Monitored payloads are stored in S3-compatible object storage.

Exit procedure

1. Export rules, policies and custom detectors via the Control API;
2. Export decision logs and the audit trail;
3. Download monitored payloads from object storage;
4. Deploy an alternative DLP solution;
5. Import the exported configurations into the new solution;
6. Delete the Numspot DLP instance.