TL;DR: Its Privacy Mode is an optional MDR configuration that prevents analyst-initiated file retrieval from SNAP Agent endpoints, reducing incidental transmission of regulated data such as ePHI, CUI, and GDPR-covered information while preserving log and metadata collection, according to Blackpoint Cyber.
Editorial analysis by NHI Mgmt Group, based on content published by Blackpoint Cyber: “Blackpoint Cyber’s Privacy Mode”.
Key questions
Q: How should organisations control MDR file retrieval when endpoints may hold regulated data?
A: Treat file retrieval as a separate access path from telemetry collection.
Q: Why does endpoint file retrieval create compliance risk in managed detection and response?
A: Because content can move from a customer endpoint into the provider’s cloud environment, where it becomes subject to different processing, retention, and access conditions.
Q: What are the signs that privacy controls in MDR are too permissive?
A: Look for workflows where analysts can retrieve files directly from endpoints without a tenant-level rule, exception approval, or audit trail.
Practitioner guidance
- Define the regulated-data boundary for MDR file retrieval Classify which endpoint artifacts may contain ePHI, CUI, FCI, CDI, ITAR-regulated data, or other sensitive content before enabling analyst-driven retrieval workflows.
- Use tenant-level enforcement for regulated scopes Apply Privacy Mode across the full tenant when all devices in scope must be protected, rather than relying on endpoint-by-endpoint exception handling.
- Validate that log-only telemetry supports investigations Confirm that system event logs, running processes, services, network connections, and other retained metadata are enough for triage when file content is blocked.
Bottom line: Privacy Mode shows how MDR can support incident response while still limiting the transfer of regulated endpoint content into a provider environment.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →