← Trust Center

InsightHire in AWS GovCloud (US)

For agencies and government contractors whose data has to stay inside a FedRAMP High boundary, we run a separate copy of InsightHire in AWS GovCloud (US). It has its own accounts, its own data and its own keys, and only US persons can administer it.

Updated November 11, 2026.

Cloud
AWS GovCloud (US)
Regions
Both GovCloud (US) regions
Administrators
US persons only
Encryption
FIPS 140 validated

How it works

  • A separate partition, not just a region

    GovCloud is its own AWS partition, with separate accounts, sign-ins and networks from the commercial cloud. Your deployment shares nothing with our commercial service: no shared database, cache, file storage, logs, backups or encryption keys.

  • The whole application inside the boundary

    Putting only the database in GovCloud would not keep your data in the boundary, because the application, logs and backups would still sit outside it. So every part of InsightHire that touches your data runs inside GovCloud.

  • Two regions for recovery

    Production runs in one GovCloud region across multiple data centers. A live copy of every database is kept in the second GovCloud region, so we can recover from the loss of a whole region without leaving GovCloud.

  • Built from the same code as production

    Our infrastructure is defined in version-controlled code that is reviewed before it changes. Your GovCloud environment is built from those same templates, so it gets the same controls as our commercial production, plus the GovCloud-specific ones below.

What runs inside GovCloud

  • Application and API servers
  • Databases, running across multiple data centers
  • Cache and background job queues
  • File storage for interview video, resumes and documents
  • Application logs and audit trails
  • Backups and the disaster recovery copy
  • Email sending
  • Secrets and encryption keys
  • The AI language model (Amazon Bedrock in GovCloud)

Security controls

What protects your data inside the GovCloud environment.

Access

  • Only US persons can administer the GovCloud environment.
  • Staff sign in through single sign-on with multi-factor authentication and short sessions. There are no long-lived access keys.
  • Emergency admin access is separate, requires MFA and raises an alert when used.
  • Account-wide guardrail policies block using any AWS region outside GovCloud.

Encryption

  • Calls to AWS services use FIPS 140 validated endpoints.
  • All traffic is encrypted in transit with TLS 1.2 or higher, including database connections.
  • Databases, file storage, backups and caches are encrypted at rest with customer-managed keys that rotate automatically.
  • Sensitive contact fields are also encrypted in the database at the field level.

Logging and monitoring

  • Every AWS API call is recorded in CloudTrail with log file validation, stored in a private, versioned, encrypted bucket.
  • An application audit log records security-relevant actions, including any access by InsightHire support. Your admins can see it.
  • Alerts for database health, failed backups and replication lag go straight to our engineering team.
  • A written incident response plan, with notice to you if your data is affected.

Backups and recovery

  • Point-in-time database restore for 35 days.
  • Daily backups are copied to a separate, locked backup account. Nobody, including us, can delete them early.
  • We test restores and time them. A restored database is typically ready in about 30 minutes.

Outside services

Anything that handles your data runs inside GovCloud, is replaced with a GovCloud-hosted option, or stays off. Before go-live you get the full list of services in your deployment, where each runs and what data it sees.

  • Sign-in

    Your users sign in with your own identity provider over SAML or OIDC, with SCIM provisioning, so passwords and MFA policy stay under your control.

  • AI

    Interview summaries and scoring use a language model hosted inside GovCloud (Amazon Bedrock). We do not train AI models on customer or candidate data today.

  • Email

    Notification email is sent from inside GovCloud (Amazon SES).

  • Everything else

    Features that depend on an outside service, such as speech-to-text, live video, phone calls or background checks, are turned on only if that service is cleared for your deployment. Otherwise they stay off.

Who does what

Security in GovCloud is shared. Here is who owns each part.

AWS

  • Physical data centers, hardware and network
  • The GovCloud (US) authorizations, including FedRAMP High
  • Screening of AWS staff who operate GovCloud

InsightHire

  • The application and its security
  • Configuration, patching and access control
  • Monitoring, backups and incident response
  • Clearing every outside service before it touches your data

Your organization

  • Your users, roles and identity provider
  • Which data you put into InsightHire
  • Retention settings for your records

Compliance

What GovCloud covers, and what it doesn’t.

  • Available on request

    We build a GovCloud deployment when a customer needs one. It is not running today, and we will tell you plainly where your deployment stands at each step.

  • FedRAMP

    AWS GovCloud (US) is FedRAMP High authorized, and that covers the infrastructure layer. InsightHire does not hold a FedRAMP or StateRAMP authorization of its own. If your agency needs one, tell us early so we can plan your review together.

  • SOC 2

    Our SOC 2 program is in place, but we have not been audited yet. The same policies and controls apply to the GovCloud deployment.

  • CJIS

    If your work involves criminal justice information, we sign the CJIS Security Addendum. Everyone with access to that data gets fingerprint-based background checks and annual security training, and your state’s CJIS Systems Agency reviews the setup.

Getting started

  1. 1

    Scoping call

    We meet with your security team to confirm which parts of InsightHire you will use, what data you will store, and which requirements apply, such as CJIS.

  2. 2

    Security review

    Under NDA, we share an architecture diagram, a data flow diagram, the list of services in your deployment, and our security policies and questionnaire answers.

  3. 3

    Build

    We build your environment in GovCloud from our infrastructure code, turn on only the cleared features, and check every control on this page.

  4. 4

    Your testing

    Your team tests sign-in, roles and your hiring workflow. If you already use InsightHire, we move your data in an encrypted, logged transfer.

  5. 5

    Go live

    After launch you get the same status page, incident notices and 30 days’ notice of any new service that will see your data.

Ready to start? Request a security review and mention GovCloud, or email support@insighthire.com.

Frequently asked questions

Is it the same InsightHire?

Yes. It is the same application your team would use in our commercial service, running as a separate copy inside GovCloud.

Can data move between the commercial service and GovCloud?

No. The two environments share no databases, storage or keys. Data moves into GovCloud only when you ask us to move an existing account, as a one-time encrypted and logged transfer.

Do candidates need an account?

No. Candidates still use a private link with a long random token. The link is served from GovCloud and only opens that candidate’s own journey.

Who at InsightHire can see our data?

Only US persons on our team, only to help when you ask, and every support access is recorded in your organization’s audit log.

Which features are available?

Most of them. A feature that relies on an outside service without a cleared option for your deployment stays off until there is one. We list these at the scoping call, before you commit.

How long does setup take?

We agree on a date at the scoping call. The environment is built from code, so most of the time goes to your security review and testing.