Netra is built for highly regulated environments. We do not want your data, and our software is architected to ensure we cannot see it.
The Netra Go-Forensic engine is compiled with zero analytics, tracking, or background Reporting modules. No health pings, no usage metrics, and no "home-phoning" ever leave the binary. All findings are generated locally on the auditor workstation and stored in the user-specified directory.
Netra uses standard LDAP and Graph API search calls. Our code contains zero "Create", "Modify", or "Delete" primitives. We are a forensic observation tool, not an administrative tool. This ensures zero risk to Active Directory forest stability or Entra ID tenant integrity.
Netra requires zero agents on Domain Controllers, Entra Connect servers, or endpoints. We do not install drivers, services, or registry keys. On execution, the tool creates a direct, encrypted connection to the target controller and terminates it immediately upon completion.
At no point is your Active Directory dump or Entra ID permission graph transmitted to a Netra-hosted server for "Processing" or "Analysis". The lens logic is executed locally, meaning your identity governance data remains within your specified air-gapped or corporate network boundary.
| Requirement | Netra Implementation |
|---|---|
| Data Locality | 100% On-Premise / Local. No Cloud processing. |
| Encryption | LDAPS (TLS 1.2/1.3) required for connection. |
| Privilege | Run as Standard User (No Admin rights needed on source). |
Compliance Note: Netra facilitates GDPR and HIPAA audits by providing visibility without increasing the attack surface. For the official SOC2 Type 2 report or more detailed security whitepapers, contact [email protected].