Security boundaries / public disclosure
Security, data handling and known limits
NEES is a governed-action decision boundary, not an all-purpose security or compliance guarantee. Applications remain responsible for identity, real target validation, external credentials, enforcement, execution and truthful outcome reporting.
Security responsibilities
- Use a trusted server for runtime keys, provider keys and exported assessment configuration; never publish secrets in client bundles, screenshots or issues.
- Treat missing, stale, rejected or unavailable governance as no permission to perform a side effect.
- A positive governance decision still requires local authorization, current-context and target checks.
- A gateway or adapter governs only mediated supported routes, not arbitrary OS/network activity.
- Report failures and uncertain outcomes accurately. Never mark executed or verified based solely on ALLOW.
Data processing and privacy
Governance requests can contain action-related context, actor/resource facts and operation identifiers. Do not submit secrets or personal/customer data beyond what the documented contract requires.
Review the Privacy Policy and Terms for published legal terms. A separate technical statement of exact retention windows, data-residency guarantees, encryption controls, subprocessor inventory and export/deletion behavior has not been established in this public documentation. Do not assume unstated guarantees.
Evidence and assurance
NEES documents supported decision evidence, execution reporting and receipts. These records are reviewable, but their mere existence does not establish cryptographic signing, immutable storage or independently verified tamper evidence.
Internal engineering tests and hosted acceptance evidence must be labeled as internal. As of this October 2026 disclosure, no public SOC 2, ISO 27001 or independent penetration-test certification is asserted here.
Operational and preview boundaries
The current Free Preview has no production/staging environment or self-service paid upgrade. There is no publicly promised uptime SLA, production availability benchmark, multi-region data residency or self-hosted Core offering here.
A timeout does not establish permission or prove execution. Avoid unbounded retries of actions with side effects; use the deployed contract's supported reconciliation and idempotency behavior.
Report a security concern
Do not post vulnerabilities, secrets, customer data or raw production traces in public GitHub issues. Use the official private security contact channel published by Nainacore; for general inquiries contact info@nees.cloud.