Specset — FedRAMP Public Information
Specset Cloud Platform (SCP) · FedRAMP 20x · Class A Certified · last generated 2026-11-12
Conforms to the FedRAMP Certification Package Overview schema (2026-06-24). Served as
application/json with no authentication, approval workflow, or access justification required.
This page publishes the information required by FedRAMP CDS-CSO-PUB (Public Information). Every enumerated field is listed below; fields that do not yet apply to Specset's current stage are stated explicitly rather than omitted.
| FedRAMP ID | FR2631258135 FedRAMP Marketplace listing | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service Model | SaaS | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Deployment Model | Public Cloud | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Business Category | Artificial Intelligence (AI), Construction | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UEI Number | S7RZBSZXNBD5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sales Contact Information | sales@specset.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Security Contact Information | FedRAMP Security Inbox · fedramp@specset.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product Website | https://specset.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product Logo | https://specset.com/fedramp/specset-logo.png | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Overall Service Description | The Specset Cloud Platform is an AI platform for construction document review. It automates technical review across project manuals, drawing sheets and shop drawings: submittal review against project specifications, UFGS (Unified Facilities Guide Specifications) compliance checking, design review automation, asset management logic, and search and question answering across a project's documents. The platform flags potential issues and returns cited answers drawn from the customer's own project documents. Specset is the trade name of Spot.xyz Corporation, formerly Specbook. The SOC 2 Type II report supporting this package is issued to Spot.xyz Corporation DBA Specset, and the Unique Entity Identifier above is registered to that entity. FedRAMP ID FR2631258135 is the only Marketplace listing for this offering; the duplicate created at intake, FR2631747321, is no longer listed. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Services and Security Categories |
Not included
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Secure Configuration Guidance | https://docs.specset.com/docs/secure-configuration Specset's Secure Configuration Guide (SCG-CSO-RSC), a public page in the product documentation written for the administrators of a customer organization: the roles that control an organization and the FedRAMP term for each, the recommended security settings for an organization that holds federal information or CUI and what each does, how Admin accounts are set up, reviewed and removed, and how account access is requested and recovered. It gives the recommended settings in JSON with the API query that exports an organization's current settings for comparison, and the version history of the recommended settings. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Documentation Overview |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Trust Center | https://trust.specset.com Access instructions: The landing page at https://trust.specset.com requires no login. FedRAMP staff and agency reviewers request access to the restricted FedRAMP Certification Data from the Trust Center page. Requests from fedramp.gov and gsa.gov email addresses are approved automatically; Specset approves all other requests manually. Specset does not require acceptance of terms or a non-disclosure agreement. If a request is not approved within one business day, email fedramp@specset.com. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Next Ongoing Certification Report Date | 2026-12-01 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Third-Party Information Resources | FedRAMP Certified (9)
Not FedRAMP Certified (13)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FedRAMP Recognized Independent Assessor | Prescient Security, LLC. (Assessor ID 202040) |
Information flows
Customer data enters only through HTTPS to Google Cloud load balancers and is processed and stored inside the Google Cloud Assured Workloads project specset-prod-assured (us-west1; Cloud Storage in the US multi-region). Kubernetes network policies limit the workloads' connections: beyond the database, cache, vector database and workflow service on the project's private network, the application server and workers may reach only the 35 hostnames on the egress allow-list, each named exactly. Which of those an organization's data may reach is decided per organization: in CUI mode, model processing, embeddings and web grounding use only Vertex AI in the Assured Workloads project at location us, and the commercial model providers, web search, the hosted scraping service, support chat and the construction integrations are disabled.
The offering is categorized Moderate. Each third-party information resource carries its own FIPS 199 category in the information-resources inventory.
| Flow | From | To | Path and controls | Data | Security category |
|---|---|---|---|---|---|
| Customer access | Customer users' browsers, the specset command-line tool and MCP clients | Application API server and static web application (inside the boundary) | HTTPS (TLS 1.2+ policy) to Google Cloud's global external Application Load Balancer; API requests pass Cloud Armor; static files come from Cloud Storage | Customer content, account data and credentials | Moderate |
| Support chat | Customer users' browsers, for organizations not in CUI mode | Intercom (United States hosting) | HTTPS from the in-app support messenger; the messenger never loads for an organization in CUI mode | Customer users' contact details and identification hashes, and support conversation content; no project documents | Moderate |
| Processing and storage | Application API server and workers | Cloud SQL for PostgreSQL, Memorystore for Redis, Qdrant, Temporal and Cloud Storage (inside the boundary) | Private addresses inside the project's VPC for the database, cache, vector database and workflow service, with TLS verified by the client on every hop; Cloud Storage through its Google API host | Customer content, documents, embeddings and workflow state | Moderate |
| AI processing for organizations in CUI mode | Application API server and workers | Vertex AI, project specset-prod-assured, location us (aiplatform.us.rep.googleapis.com); provisioned and not enabled: Amazon Bedrock in AWS GovCloud (US) and the Azure OpenAI US Data Zone deployments | HTTPS, no static keys: Workload Identity for Vertex AI; for the routes provisioned and not enabled, an AWS GovCloud (US) role assumed through Google web identity (Amazon Bedrock) and a federated managed identity with key authentication disabled (Azure OpenAI) | Prompts, document content and embeddings | Moderate |
| AI processing for other organizations | Application API server and workers | Vertex AI (commercial route, project specbook-production, global), Amazon Bedrock, Azure OpenAI, Cloudflare Workers AI, Google AI Studio, and Perplexity for web search | HTTPS to each provider's listed hostnames only | Prompts and document content of organizations not in CUI mode | Moderate (each provider's category is in the inventory) |
| Application workers and API server | Amazon SES (us-west-2); for email received at project addresses, the receiving S3 bucket and SQS queue (workers only) | HTTPS; federated AWS role, no static keys | Recipient addresses and notification content, and email received for project addresses; notifications to organizations in CUI mode carry no project content, and those organizations have no project address | Moderate | |
| Customer sign-in | Application API server | Google Sign-In and Microsoft Entra ID; and an organization's own OpenID Connect provider, such as Okta, once Specset has added that provider's hostnames to the egress allow-list at the organization's request (none added as of this edition) | HTTPS (OpenID Connect). The user signs in at the provider in the browser; the API server fetches the provider's discovery document and signing keys and redeems the authorization code, at hostnames on the egress allow-list only. | Authorization codes, identity tokens and profile claims | Moderate |
| Customer-initiated integrations and public data | Application API server and workers | Procore and Autodesk Platform Services (the customer's own tenant; disabled in CUI mode), Firecrawl (public bid portals; disabled in CUI mode), NOAA and National Weather Service APIs (project-site coordinates) | HTTPS to each service's listed hostnames only | As described for each in the inventory | Moderate or Low, per the inventory |
| Website inquiries | Application API server | Slack (incoming webhook) | HTTPS to hooks.slack.com only | Prospect contact details from the public website's contact form; no customer content or customer-user data | Moderate |
| Administration | Specset's two founders | Cluster and administrative interfaces | Identity-Aware Proxy (Google Workspace sign-in with security keys) for the workflow console; Connect Gateway to the private cluster control plane; per-task administrative access through Privileged Access Manager | Operational metadata; customer data through the founders' read identities (stored files through the gcs-reader service account; database rows of organizations not in CUI mode through the read-only inspection tunnel, approved per session) and through per-task administrative access under Privileged Access Manager | Moderate |
| Engineering assistants | Claude Code, OpenAI Codex, Google Antigravity and Cursor on operator laptops (the two technical founders and, since 2026-10-23, a developer) | Anthropic, OpenAI, Google and Anysphere (Cursor) model inference (Anthropic's and OpenAI's APIs offer no processing-region selection; the processing regions of the Google Antigravity and Cursor services are not verified) | What the assistant reads with the operator's own access is sent to its provider. In Claude Code, Codex and Antigravity, repository settings and hooks run infrastructure reads as the read-only service account, and database rows come through the SELECT-only, time-limited tunnel. The operator approves its start in Claude Code or starts it from their own terminal; the Codex and Antigravity hooks refuse the start. In Cursor, a fail-closed repository hook refuses the known paths to production, customer data (local copies included) and credentials. The hooks read command text, so Google Cloud IAM and the application's recorded, alerted CUI opt-in bound what a script using the operator's credentials can reach | Source code, operational data and, in Claude Code, Codex and Antigravity, what the operator has the assistant read, which can include customer data of organizations not in CUI mode; Cursor is held to source code by rule and hook. Data of organizations in CUI mode must not reach an engineering assistant: the read-only service account cannot read their database rows, customer documents or secret values, and sees their application log entries only as sanitized copies | Moderate |
Permitted connections (MAS-CSO-FLO): every permitted connection between the offering's components and to external resources, generated from the deployed configuration, with the code and the derivation. Listed under documentation.
Policies and procedures
Every policy and procedure in the FedRAMP Certification Data (CDS-CSO-IRP), with the version and word count of the edition currently supplied. The availability column says how to obtain each; restricted documents are requested on the trust center or from the security contact above.
| Name | File | Summary | Words | Version | Last updated | Related FedRAMP practices | Availability |
|---|---|---|---|---|---|---|---|
| Incident Response Procedure Procedure | incident-response.pdf | Incident detection, triage, FedRAMP reportability evaluation, initial, ongoing and final incident reports, the FedRAMP Security Inbox procedure and the quarterly review. | 4029 | 2026-11-12 | 2026-11-12 | IEC-CSO-EFR, IEC-CSO-EFI, IEC-CSO-DPR, IEC-CSO-IIR, IEC-CSO-OIR, IEC-CSO-FIR, IEC-CSO-AIR, AFC-CSO-INB, AFC-CSO-NOC, AFC-CSO-TFG, AFC-CSO-RCV, AFC-CSO-CRA, AFC-CSO-EMR, AFC-CSO-IMA, AFC-CSO-ACK, CDS-UTC-AAD, KSI-INR-RIR, KSI-INR-AAR, KSI-INR-RPI | Trust center (https://trust.specset.com), restricted resource open to access requests, no NDA. |
| Vulnerability Management Procedure Procedure | vulnerability-management.pdf | Persistent vulnerability detection, PAIN-based evaluation, response timeframes, exceptions and risk acceptance, and the monthly vulnerability activity report. | 5482 | 2026-11-12 | 2026-11-12 | VDR (all rules), VER (all rules) | Trust center (https://trust.specset.com), restricted resource open to access requests, no NDA. |
| Recovery plan (Recovery and Backup Configuration) Plan | 12-recovery-and-backup-configuration.pdf | Service recovery objectives, backup configuration by datastore, recovery procedures and the recovery testing cadence. | 1340 | 2026-10-20 | 2026-10-20 | KSI-RPL-ARP, KSI-RPL-RRO, KSI-RPL-ABO, KSI-RPL-TRC | Trust center (https://trust.specset.com), restricted resource open to access requests, no NDA. |
| Secure Configuration Guide Procedure | https://docs.specset.com/docs/secure-configuration | For the administrators of a customer organization: the accounts that control an organization, the recommended security settings for one holding federal information or CUI, and how account access is requested and recovered. | 1707 | 2026.09.18.2 | 2026-11-10 | SCG-CSO-RSC, SCG-CSO-PUB, SCG-CSO-AUP, SCG-ENH-VRH | Public documentation page, no login. |
| Ongoing Certification Reports and Quarterly Reviews Procedure | ongoing-certification-reports.md | How the quarterly Ongoing Certification Report is assembled, checked for sensitive information and published, how questions about it are answered, the reviews held in the same quarterly slot and the Class C Quarterly Review. | 1417 | edition 2026-11-12 | 2026-11-12 | CCM-OCR-AVL, CCM-OCR-NRD, CCM-OCR-SOR, CCM-OCR-FBM, CCM-OCR-AFS, CCM-OCR-LSI, CCM-OCR-RPS, CCM-QTR-MTG, CCM-QTR-SAR, CCM-QTR-REG, CCM-QTR-NRD, CCM-QTR-ACT, CCM-QTR-RTR, CCM-QTR-RTP, CCM-QTR-NID, CCM-QTR-SCR, CCM-QTR-SRR, CDS-CSO-HAD, CDS-CSO-RIS, CPO-CSX-CPM, KSI-CMT-RVP | Class C package procedure; supplied on request to fedramp@specset.com until the Class C package is filed with it. |
| Significant Change Notification procedure Procedure | significant-change-notification.md | How each production change is evaluated for significance, confirmed by an operator, recorded and, when significant, notified. | 3328 | edition 2026-11-12 | 2026-11-12 | SCN (all rules), KSI-CMT-LMC | Class C package procedure; supplied on request to fedramp@specset.com until the Class C package is filed with it. |
| Use of representative samples Procedure | use-of-representative-samples.md | Every place where Specset's own verification and validation looks at a sample instead of a whole population, and why the sample stands for the rest. | 489 | edition 2026-10-17 | 2026-10-17 | IVV-CSO-USR, IVV-CSO-DUS | Class C package procedure; supplied on request to fedramp@specset.com until the Class C package is filed with it. |
| Privileged access procedure Procedure | privileged-access.md | How the founders obtain administrative access to production per task, with a reason and for a limited time, through Privileged Access Manager, and the last-resort path. | 4104 | edition 2026-11-10 | 2026-11-10 | KSI-IAM-JIT, KSI-IAM-ELP | Class C package procedure; supplied on request to fedramp@specset.com until the Class C package is filed with it. |
| Access Control Policy Policy | Access Control Policy (Vanta policy document) | Limits access to information and information-processing systems, networks and facilities to authorized parties, including account management, authentication and password requirements. | 2719 | 3.1 | 2026-09-11 | KSI-IAM-AAM, KSI-IAM-APM, KSI-IAM-ELP, KSI-IAM-JIT, KSI-IAM-SNU, KSI-IAM-SUS, KSI-MLA-ALA | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Asset Management Policy Policy | Asset Management Policy (Vanta policy document) | Identifies the organization's assets and who is responsible for protecting them, and prevents unauthorized disclosure, modification, removal or destruction of information on media. | 558 | 4.0 | 2026-11-06 | MAS-CSO-IIR, KSI-PIY-GIV | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Business Continuity and Disaster Recovery Plan Plan | Business Continuity and Disaster Recovery Plan (Vanta policy document) | Continuity of critical services in a disaster, the responsibilities and communications, and the recovery time and recovery point objectives. | 2386 | 3.1 | 2026-09-14 | KSI-RPL-ARP, KSI-RPL-RRO, KSI-RPL-ABO, KSI-RPL-TRC, KSI-CNA-OFA | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Code of Conduct Policy | Code of Conduct (Vanta policy document) | The conduct expected of all staff, for safe and collaborative working conditions, and the consequences of unacceptable behavior. | 1117 | 4.0 | 2026-11-06 | — | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Cryptography Policy Policy | Cryptography Policy (Vanta policy document) | Requirements for cryptographic keys and methods across the encryption lifecycle, so that cryptography protects the confidentiality, authenticity and integrity of information. | 426 | 4.0 | 2026-11-06 | CMU-CSO-CMD, CMU-CSO-UVM, KSI-SVC-SIN, KSI-SVC-VCM, KSI-SVC-ASM | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Data Management Policy Policy | Data Management Policy (Vanta policy document) | Classification, protection, retention and secure disposal of information according to its importance; version 3.3 amends the retained version 3.0 text. | 3197 | 3.3 | 2026-11-10 | KSI-SVC-RUD, KSI-SVC-SIN | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Human Resource Security Policy Policy | Human Resource Security Policy (Vanta policy document) | Screening, security responsibilities, training and suitability of personnel and contractors, before, during and after employment. | 1024 | 3.1 | 2026-10-12 | KSI-CED-RAT | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Incident Response Plan Plan | Incident Response Plan (Vanta policy document) | The organizational plan for managing information security incidents and events; version 3.1 amends the retained version 3.0 text, and the Incident Response Procedure carries the FedRAMP reporting steps. | 5453 | 3.1 | 2026-09-14 | IEC (all rules), KSI-INR-RIR, KSI-INR-AAR, KSI-INR-RPI | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Information Security Policy (Acceptable Use) Policy | Information Security Policy (AUP) (Vanta policy document) | The company's information security policies and the acceptable use and protection of its information and assets, including mobile devices. | 2531 | 4.0 | 2026-11-06 | — | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Information Security Roles and Responsibilities Policy | Information Security Roles and Responsibilities (Vanta policy document) | Who in the company is responsible for which part of information security, so that policies are communicated and responsibility is clearly assigned; version 3.1 names the holder of the IT Manager role and retains the version 3.0 text. | 1082 | 3.1 | 2026-11-06 | KSI-PIY-RES | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Operations Security Policy Policy | Operations Security Policy (Vanta policy document) | Secure operation of information-processing systems, including change management, logging and monitoring, malware and vulnerability handling and data leakage prevention. | 3497 | 3.2 | 2026-10-12 | KSI-CMT-LMC, KSI-CMT-RVP, KSI-MLA-LET, KSI-MLA-RVL | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Physical Security Policy Policy | Physical Security Policy (Vanta policy document) | Prevents unauthorized physical access to, and damage to, the organization's information and information-processing facilities; production facilities are Google Cloud's. | 753 | 5.0 | 2026-11-06 | — | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Risk Management Policy Policy | Risk Management Policy (Vanta policy document) | How information security risks and opportunities are identified and treated, and the plan for reaching the security and privacy objectives. | 2686 | 4.0 | 2026-11-06 | — | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Secure Development Policy Policy | Secure Development Policy (Vanta policy document) | Security designed and implemented within the development lifecycle of applications and information systems. | 976 | 3.1 | 2026-10-12 | KSI-PIY-RSD, KSI-CMT-VTD, KSI-SCR-MIT | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
| Third-Party Management Policy Policy | Third-Party Management Policy (Vanta policy document) | Protection of data and assets shared with, accessible to or managed by suppliers, and the agreed level of security and service in supplier agreements. | 1331 | 4.0 | 2026-11-06 | MAS-CSO-TPR, KSI-SCR-MIT, KSI-SCR-MON | Approved and maintained in Vanta with employee acceptance records; supplied on request to fedramp@specset.com. |
Cryptographic modules
Each place where cryptography protects federal customer data in the Specset Cloud Platform, the module that performs it and its status under the NIST Cryptographic Module Validation Program (CMVP). Modules that Google operates inside its services are BoringCrypto: Google states that it holds FIPS 140-3 certificate 5104, which NIST lists as active, and Google Cloud KMS keys at the software protection level use the same module. Which certificate covers the build behind each Google service is Google's statement, which Specset relies on and cannot test. Since 2026-10-30 the application's Node.js processes run in FIPS mode on the OpenSSL FIPS Provider, FIPS 140-3 certificate 4985, for the TLS connections Node.js makes and its node:crypto calls. The other TLS libraries inside the containers Specset runs (the workflow service and its tools, the vector database, the workflow SDK's core, the certificate issuer and the database proxy) are not CMVP-validated as deployed, and inside the application the check of a password not yet rehashed and one-time-password codes use code outside the validated module, while the encryption of authenticator secrets uses the provider but not in its approved mode, because the application supplies the AES-GCM IV that the certificate's security policy has the module generate. The list was checked against the information-resources inventory and the Terraform configuration on 2026-10-07; its administrative load-balancer and commercial Vertex AI entries against the inventory edition 2026-10-27 and the Terraform configuration on 2026-10-28; its component versions against the deployed workloads on 2026-11-12; certificate status and component releases are re-read at each quarterly Ongoing Certification Report.
| What it protects | Module | Operated by | NIST CMVP status |
|---|---|---|---|
| Data at rest: Cloud SQL application and workflow databases and their backups. AES-256 under a customer-managed Cloud KMS key, software protection level, rotated every 90 days. | BoringCrypto (Cloud KMS, Cloud SQL) | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services | |
| Data at rest: Kubernetes Secrets in GKE etcd, including service credentials and the in-cluster certificate authority's private key. Application-layer encryption under a customer-managed Cloud KMS key, rotated every 90 days. | BoringCrypto (Cloud KMS, GKE) | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services | |
| Data at rest: Cloud Storage (customer documents and the audit-log archive), Cloud Logging buckets, Memorystore, Persistent Disk (search-embedding volumes and GKE node boot disks), Secret Manager and the Terraform state bucket. Google default encryption, AES-256. | BoringCrypto | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services | |
| Data in transit: users' browsers to the service. TLS 1.2 or later at Google's global HTTPS load balancer under a restricted SSL policy. The hop from the load balancer to the application is inside Google's network, and its protection is Google's and inherited. | Google Front End TLS (BoringSSL, whose core is BoringCrypto) | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services | |
| Data in transit: users' browsers to Cloud Storage. Documents are uploaded and read directly with signed URLs; TLS ends at Google's API front end under Google's own TLS configuration. | Google Front End TLS (BoringSSL, whose core is BoringCrypto) | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services | |
| Data in transit: application and workers to Cloud SQL. TLS 1.2 or later with the server certificate verified against the instance's own certificate authority; the instance refuses unencrypted connections. | Clients: the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30; Go's standard TLS library in Temporal 1.32.2. Server: Cloud SQL. | Specset (clients); Google (server) | Validated for the application's client: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; not CMVP-validated as deployed (not built or run in an approved mode) for Temporal's client; the server side is Google's, and Specset makes no separate claim for it |
| Data in transit: application to Memorystore for Redis. TLS only, with AUTH; the application verifies each server certificate against that instance's certificate authority. | Client: the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30. Server: Memorystore. | Specset (client); Google (server) | Validated for the client: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; the server side is Google's, and Specset makes no separate claim for it |
| Data in transit: application and workers to the Qdrant vector database, and between Qdrant peers. TLS from the in-cluster certificate authority, an API key for clients and mutually authenticated TLS between peers. | Client: the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30. Server and peers: rustls as built into Qdrant 1.19.2. | Specset | Validated for the client: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; server and peers not CMVP-validated as deployed (not built or run in an approved mode) |
| Data in transit: to the Temporal workflow service and between its services. TLS from the in-cluster certificate authority, verified by every client. | Server: Go's standard TLS library in Temporal 1.32.2. Clients: the Temporal TypeScript SDK 1.25.0 in the application image (worker connections through the SDK's Rust core on rustls; client connections on the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30); Go's standard TLS library in the Temporal web UI 2.58.1, the Temporal admin tools 1.32.2 and the autoscaler (KEDA 2.21.0). | Specset | Validated for the application's client connections: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; the rest not CMVP-validated as deployed (not built or run in an approved mode) |
| Data in transit: in-cluster certificate authority. cert-manager v1.21.3 issues the Temporal, autoscaler and Qdrant certificates (ECDSA P-256). | Go's standard cryptography library in cert-manager v1.21.3 | Specset | Not CMVP-validated as deployed (not built or run in an approved mode) |
| Data in transit: administrative path to Cloud SQL. An operator's session reaches the in-cluster Cloud SQL Auth Proxy through a TLS-protected port-forward over Connect Gateway; the proxy carries it to the instance over TLS 1.3 with verified client and server identities. | Go's standard TLS library in Cloud SQL Auth Proxy 2.26.3 and in kubectl on the operator's machine; Google Front End TLS for Connect Gateway. | Specset (proxy, kubectl); Google (Connect Gateway) | Not CMVP-validated as deployed (not built or run in an approved mode) for the Go library; Google's front end as above |
| Data in transit: administrative browser path to the workflow console, behind Identity-Aware Proxy on a second global HTTPS load balancer with the same restricted SSL policy. Behind it, the hop to the workflow console is inside Google's network and inherited. Until 2026-10-26 the same path also reached the vector database's API, without the load balancer verifying the database's certificate; that path was retired that day. | Edge: Google Front End TLS. | Validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services. | |
| Data in transit: calls from the application to Google APIs inside the boundary (Vertex AI on the assured route, Cloud Storage, and the IAM Credentials API that signs Cloud Storage URLs), and, for organizations not in CUI mode only, to Vertex AI in the peer project specbook-production at location global. | Client: the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30. Server: Google Front End TLS. | Specset (client); Google (server) | Validated for the client: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; server validated: BoringCrypto, FIPS 140-3 certificate 5104 (active, validated 2025-12-09; certificate 4735 also active), as Google states for its services |
| Data in transit: calls from the application to services outside Google Cloud listed under third-party information resources (for example Amazon SES, customer identity providers and, for organizations not in CUI mode, the commercial model and integration providers). | Client: the OpenSSL FIPS Provider, loaded by Node.js in FIPS mode since 2026-10-30. Server side and storage: the provider's own modules. | Specset (client); the provider (server) | Validated for the client: OpenSSL FIPS Provider, FIPS 140-3 certificate 4985 (The OpenSSL Project; Level 1; active, sunset 2030-03-10), in its approved mode; the provider's modules are covered by its own FedRAMP certification where the resource is listed as certified |
Package metadata
| Accountable official | Gordon Hempton, CEO and Co-Founder · gordon@specset.com |
|---|---|
| Version | 2026.11.12 |
| Last updated | 2026-11-12T21:40:00Z |
| Source of update | github.com/specsetai/fedramp-marketplace (main branch; schema-validated by the repository's validate workflow; published to specset.com/fedramp/). Version 2026.11.12, published with Security Decision Record v2026.09.14.18, follows version 2026.11.10. Since 2026.11.10: the policy and procedure reference gives the Incident Response and Vulnerability Management Procedures at edition 2026-11-12 and the current editions of the Ongoing Certification Reports and Quarterly Reviews and Significant Change Notification procedures; the cryptographic module list gives the component versions read from the deployed workloads on 2026-11-12 (Temporal 1.32.2, Temporal web UI 2.58.1, Temporal admin tools 1.32.2, cert-manager v1.21.3, Cloud SQL Auth Proxy 2.26.3, Temporal TypeScript SDK 1.25.0); the AWS supporting-services entry drops the legacy database-backup bucket, deleted on 2026-11-09; the Azure entry states the route for organizations in CUI mode to the US Data Zone deployments, provisioned and not enabled, and Microsoft's default abuse-monitoring storage with Specset's plan for it; the Google Cloud entry gives the location of the commercial Vertex AI route (global); the information flow for organizations in CUI mode names the two routes that are provisioned and not enabled; and the example Ongoing Certification Report's summary says the first report is planned for 2026-12-01 and due no later than 2026-12-04. Earlier versions are in this repository's history. |