.NET Security
Keep .NET enrollment and remote tools limited to trusted developer builds.
Enrollment uses clear-text UDP and ws://. Run it only on a trusted local
development network.
- Initialize Ansight only in approved developer variants.
- Set
AnsightRemoteToolsPolicydeliberately and keep a runtime deny-all guard in protected builds. - Prefer read-only tool suites.
- Do not embed connection JSON, certificates, keys, or host addresses.
- Store registration state only through the SDK’s platform-private storage.
- Revoke registrations through the host or clear app data when a device should stop reconnecting.
- Keep cellular host connections disabled unless the workflow intentionally uses mobile data or a personal hotspot.
- Keep unattended provisioning disabled outside trusted test runners, and never log its one-use bearer payload.
- Treat crash messages, traces, breadcrumbs, and metadata as sensitive. Disable crash capture, host handoff, or offline attachment when policy requires it.
On Android, use the SDK scanner integration without adding unrelated permissions. On iOS and Mac Catalyst, add only the privacy descriptions needed by the scanning and local-network features the app actually invokes.
Native crash reports are bounded and stored in platform-private app files until delivery or expiry. See Crash Capture.