Security and data
Your compliance data belongs to you, runs in your infrastructure, and is not accessible to INTS2.
Isolated instance per company
Each company runs its own dedicated FSO Console instance in its own Google Cloud project. There is no shared application or database between organizations.
No INTS2 remote access
INTS2 has no remote access, admin connection or recovery key to any instance. Deployment runs under your own Google account; after that, INTS2 has no way into your instance or its data.
Offline Authorization Codes
Codes are ECDSA P-256 signatures created in a Google Cloud KMS hardware security module and verified offline in your instance. They contain only opaque IDs, the user's email, CAGE and term.
Full export, always
Export all of your records at any time from the app, even after a license ends. After a 7-day read-only grace period, editing pauses until a new code is installed — viewing and export always remain.
Your data stays in your project
Everything FSO Console writes is stored in your Google Cloud project, under access controls you manage. INTS2 holds only your account, signed-agreement and billing records — never your compliance data.
Designed to support NIST SP 800-171
FSO Console is designed to support organizations operating under NIST SP 800-171. It is not certified or assessed against any framework; consult your security team about your own requirements.
This website
- Served only over HTTPS with strict transport security.
- No advertising, analytics or tracking cookies, and no third-party scripts or fonts.
- Signatures are kept in an append-only, tamper-evident record.
- Contact-form messages are stored by INTS2, not a third-party form service. Please don't send CUI or classified information.