Frequently asked questions
Common questions from FSOs and their teams about FSO Console, licensing and deployment.
Deployment and setup
Do I need to manage Google Cloud infrastructure myself?
You need a Google Cloud account with billing enabled and permission to create a project. The Owner receives a deployment kit that runs in Google Cloud Shell and provisions everything — you answer a few prompts rather than wiring up servers or databases.
How long does initial setup take?
It depends on your organization's Google Cloud environment and internal approvals. The deployment itself is guided, step by step.
Who is the Owner?
The person designated to deploy and administer the company instance — one Owner per CAGE. The Owner receives the deployment kit and approves the other users on the instance.
What does running my instance cost in Google Cloud?
Your instance runs in your own Google Cloud project and is billed to your Google account by Google. Costs depend on your usage and the options you choose; the deployment kit uses small, low-cost defaults.
Licensing and Authorization Codes
What is an Authorization Code?
A digital signature created in a Google Cloud KMS hardware security module and verified offline inside your instance. It contains only opaque IDs, the user's email, CAGE and license term.
How do I get my Authorization Code?
Right after you sign. It appears on screen with Copy and Download buttons, and only you can see it. For security, codes are never sent by email; the email you receive just says your code is ready and where to view it.
Can we share one code?
No. Each code is bound to one person's email and CAGE, and sharing is prohibited by the agreement.
Can a code be changed or revoked?
Codes are signed offline and can't be changed after issue. A new code is issued for changes, and lost codes are replaced on request.
Do licenses auto-renew?
Paid subscriptions do, until you cancel; beta, trial and complimentary codes don't. Shortly before a code expires, your instance fetches the next one from FSOConsole.com by itself (or the Owner pastes it, if the automatic check is turned off). If you cancel or a payment fails, no new code is issued: the current one runs to its end date, then 7 days read-only, then editing pauses until you license again. Viewing and export always remain.
How does renewal work?
Automatically. The instance sends only its current code and gets the next one back; no records, users or documents are sent. You can cancel auto-renewal on your order page at app.fsoconsole.com at any time; to stop the next renewal, cancel at least 30 days before an annual end date or 5 days before the end of the month for month-to-month. If the agreement is updated, users sign the new version once before renewals continue.
Data and privacy
Can INTS2 access our compliance records?
No. INTS2 has no remote access, admin connection or recovery key to any customer instance.
What happens to our data if our license expires?
It stays in your Google Cloud project. Viewing and export always remain available, regardless of license status.
What does INTS2 keep about us?
Your account details, the names, emails and CAGEs of licensed users, signed-agreement records, orders and the list of issued codes — never your compliance data.
Compliance and scope
Which regulations does FSO Console support?
FSO Console is built around the record-keeping and reporting obligations of a NISPOM / 32 CFR Part 117 program.
Is "Ask the ISR" an official DCSA source?
No. It is an AI assistant that offers guidance on industrial-security questions. It is not legal advice, not an official DCSA position, and not a substitute for your assigned DCSA Industrial Security Representative. Do not enter CUI or classified information.
Does FSO Console replace the need for an FSO?
No. It is a tool for Facility Security Officers, not a substitute for one, and it does not make compliance decisions.
Still have questions? Contact INTS2.