This guide tells B3IQ customers how to configure B3IQ securely and explains the security impact of the settings that only top-level administrators can change.
Purpose and scope
Covered services: Customer Website and Dashboard, Control Plane API, Machine Agent, and Chat Assistant.
Not covered: the physical security of the facilities where B3IQ hosts customer-owned machines, and the facilities of third-party cloud providers.
FedRAMP's Secure Configuration Guide rules apply to Class B, C, and D. They are not required at Class A, so this guide prepares NPC Labs for the planned move to Class B.
Account and access settings
Access, configure, operate and decommission the top-level account
- Sign in only through the B3IQ website, with extra-login verification (MFA) turned on.
- Keep the number of top-level administrators to the minimum needed. Give everyone else the lowest role that fits: viewers read, operators do limited operational work, admins do higher-risk actions. An action is rejected when its permission cannot be established.
- Review who holds each role at least quarterly, and remove access the day someone leaves.
- To decommission an administrator, remove the role, revoke their access keys, and confirm their sessions have ended.
Settings and their security impact
| Setting | Recommended | Why it matters | Who can change it |
|---|---|---|---|
| MFA | On for every user | Stops a stolen password from giving full access | Top-level admin |
| User roles | Lowest role that fits | A compromised high role can take higher-risk actions | Top-level admin |
| Access keys | One per use, rotated and revoked when unused | A key routes requests to the customer's own machines and records usage; a leaked key lets others use that capacity | Key owner or admin |
| Key storage | Secret store only; never code, chat, logs or support bundles | B3IQ shows a key once and cannot recover it; replace it by creating a new key and revoking the old one | Top-level admin |
| Local console password | 10 to 256 characters, unique | A reset replaces recovery codes and ends all sessions | Local administrator |
| Terminal and SSH access | Limit to top-level administrators | Top-level administrators can SSH in, and administrators also have an interactive terminal in the web interface. On KVM machines the terminal reaches the B3IQ host machine, not the customer's, but the host can control the customer's machine. On bare metal machines it is the same environment. | B3IQ |
| Support access | No temporary grants are issued | B3IQ staff troubleshoot over SSH and through an onsite admin server that can restart or access machines | Not applicable |
Machine Agent and machine configuration
Customers own the machines in the B3IQ network, and B3IQ hosts and operates them. Each machine is provisioned from B3IQ's own machine image. When a machine is created, the image sets up its connection to B3IQ, its identity, signed software and updates automatically, so there are no enrollment or claim code steps for customers.
Chat Assistant and data sharing
B3IQ uses AI in two separate ways. Customers should know where their data goes.
- Internal agents: B3IQ uses internal agents for debugging and for proactively catching issues in its codebase. These agents use Anthropic models through OpenRouter.
- Machine inference: customers can install inference on a machine and chat with it. This inference runs locally, stays on B3IQ's servers and is not sent to Anthropic or OpenRouter.
- Provider terms: the retention and no-training terms for Anthropic and OpenRouter are still open in the supplier register.
Logging and activity records
B3IQ records staff activity, including unsuccessful actions, and records usage for each customer access key.
| Record | Retention | Notes |
|---|---|---|
| Administrator activity | 365 days | Currently recorded manually; not described as append-only |
| Email and build records | 90 days | Internal; email is sent through Resend |
| Playground | 30 days | There is no retention policy for other inference. A policy that includes encryption is being developed for new inference. |
Customers should keep their own logs for their accounts and machines, and review access key usage for activity they do not recognize.
Data handling, backup and recovery
- Where data goes: accounts, orders and machine records are stored in company systems. Suppliers receive only what they need for payments, signatures, email and identity checks.
- Machine requests: ordinary machine requests pass through memory and are not kept as saved content.
- Backups: B3IQ keeps a daily encrypted copy of the platform database and the identity database outside the primary cloud provider.
- Recovery: Backups are tested for recoverability.
Reporting security issues
Report suspected key leaks, unauthorized access or vulnerabilities to reports@b3iq.org. If an access key may be exposed, revoke it first, then report it.
