Security evidence, published in the open.

Papyrus provides project membership, organization membership, invitation, credential, and role records. Deploying organizations remain responsible for identity proofing, account approval, periodic review, disablement policy, and upstream identity-provider lifecycle management.

The daemon enforces authenticated sessions and project-scoped RBAC before protected operations. REST and WebSocket operations are evaluated against the caller identity and assigned project permissions.

Papyrus exposes role-based project permissions and separates ordinary member actions from administrative operations. Customers define role assignments, privileged administrators, and separation-of-duties policy.

Papyrus applies request rate limits to authentication-sensitive endpoints and rejects invalid challenges and credentials. Customers configure upstream IdP, reverse-proxy, and enclave account-lockout thresholds.

Papyrus issues bounded sessions and supports explicit logout and credential revocation workflows. Deployment owners set session lifetime, inactivity, and emergency termination requirements.

Profile-gated authentication supports CAC/PIV for SIPRNet/IL6, CAC/PIV and WebAuthn for NIPRNet/IL4, and WebAuthn, OIDC, or SAML for commercial deployments. Authentication strength depends on customer-selected providers and configuration.

Papyrus binds an externally authenticated identity to a locally generated member public key and records provenance for the binding. Customers remain authoritative for enterprise identifiers and reassignment policy.

Papyrus supports WebAuthn credential enrollment and removal, CAC/PIV certificate validation, OIDC key discovery, and SAML IdP certificates. Customers control certificate issuance, trust anchors, provider keys, recovery, rotation, and revocation.

Commercial deployments may federate external identities through OIDC or SAML. The customer determines whether non-organizational access is permitted and configures federation claims, assurance requirements, and sponsorship.

Papyrus defines security-relevant audit events for authentication, membership, role changes, project lifecycle, canvas mutation, agent and skill execution, export, configuration, and integrity verification.

Audit records identify time, actor, action, target, outcome, project context, and integrity-chain data where applicable. Secrets, raw authenticators, private keys, and bearer tokens are excluded from normal audit content.

Authorized users can retrieve and review project audit history and verify the audit chain. Customers establish review cadence, alert rules, escalation paths, and correlation with enclave monitoring systems.

Papyrus records ISO 8601 timestamps from the host operating system. Accurate, synchronized, and authoritative time is inherited from the deployment platform and must be configured by the customer.

Papyrus uses append-oriented, hash-linked audit records to make modification detectable. Customers protect database files, exports, backups, host access, and external log destinations.

The daemon generates audit records at server-side enforcement points for supported security and business operations, allowing consistent collection regardless of client interface.

Papyrus provides profile-driven defaults for commercial, NIPRNet/IL4, and SIPRNet/IL6 modes. Customers document the approved deployment manifest, operating system, container, network, IdP, model endpoint, service binding, and storage configuration.

Papyrus configuration is file- and environment-driven and can be version controlled. Approval, testing, deployment, rollback, and emergency-change processes are customer operational responsibilities.

Administrative and project permissions restrict application-level changes. Repository, deployment pipeline, host, secret-store, and production configuration access are controlled by the customer.

PAPYRUS_PROFILE gates authentication, model endpoint, internet use, agent availability, and cross-domain features. Customers set secure values and validate them against the authorized environment.

Papyrus can disable agents, external model endpoints, internet-assisted discovery, and cross-domain export by profile. Customers remove unused services, block unnecessary ports, and constrain runtime capabilities.

Papyrus publishes a lockfile and can produce SPDX or CycloneDX SBOMs for application dependencies. Customers add operating system, container, hardware, IdP, database, model server, and infrastructure components.

Papyrus supports explicit service binding, profile-based internet restrictions, authenticated project-scoped WebSocket sessions, and no required public discovery or relay infrastructure. Firewalls, proxies, segmentation, CDS boundaries, and enclave routing remain customer controls.

Browser, API, and realtime WebSocket traffic can use TLS through the authoritative Papyrus service. Customers provision certificates, approved cipher policy, termination architecture, and any required FIPS-validated modules.

Papyrus uses a deployment identity for session and transfer signing, TLS certificates, SAML certificates, OIDC verification keys, trusted deployment identities, and a pinned license authority key. Customers define key custody, approved generation, backup, rotation, revocation, escrow, and destruction.

Papyrus relies on platform cryptographic implementations for TLS, WebAuthn, X.509, token signatures, signed licenses, and QUIC. Algorithm availability does not itself establish FIPS validation; customers select validated modules when required.

Papyrus binds requests to validated session tokens, protects state-changing browser flows with CSRF challenges, validates WebAuthn challenges, and validates OIDC state and PKCE data.

Papyrus stores projects, credentials, audit records, and configuration locally. Encryption at rest is inherited from customer-managed full-disk, volume, database, or platform encryption and associated key management.

Beag Labs tracks application and dependency defects, publishes updated releases, and maintains lockfile changes. Customers define patch windows, test updates, deploy remediations, and document risk acceptance.

Papyrus exposes audit, authentication, collaboration-session, agent, transfer, and integrity events suitable for operational monitoring. Customers collect, retain, correlate, alert on, and respond to those events in their monitoring platform.

Papyrus supports deterministic dependency resolution, signed-license validation, bundle verification, and hash-linked audit verification. Customers verify release provenance, hashes or signatures, container provenance, and deployment integrity.

The daemon validates authentication responses, request bodies, project permissions, cross-domain bundles, node types, and security-sensitive configuration before processing.

Papyrus returns bounded error responses and avoids intentionally exposing private keys, tokens, or internal credential material. Customers configure production logging and reverse proxies to prevent diagnostic leakage.

Beag Labs performs source, dependency, license, and SBOM analysis and remediates supported product vulnerabilities. Customers scan deployed hosts, containers, infrastructure, model servers, and customer integrations.

The repository includes type checking, linting, unit tests, daemon tests, authentication verification paths, and dependency review. Release evidence should record executed checks and known exceptions.

Papyrus records dependency versions in pnpm lockfiles and is designed to publish SBOMs and release hashes. Beag Labs maintains source-to-release traceability; customers preserve artifacts and verify them during intake and deployment.