Information Security & Cryptography Policy
ISO/IEC 27001:2022 and SOC 2 Type II aligned cryptographic, identity, network, and SDLC controls protecting embargoed manuscripts and royalty ledgers.
Executive Summary & CISO Assurance Baseline: Publishing organisations entrust British Noble with two of the highest-risk asset classes in commercial enterprise software: pre-publication embargoed manuscripts (including market-moving non-fiction, scholarly breakthroughs, central-bank monographs, and flagship memoirs) and global contributor tax and banking vaults. British Noble's Information Security Management System ("ISMS"), governed directly by the Chief Information Security Officer (CISO) and audited continuously, aligns structurally to ISO/IEC 27001:2022, AICPA SOC 2 Type II Trust Services Criteria, Cloud Security Alliance CAIQ v4, and NIST SP 800-53 Rev. 5.
Every tenant workspace is isolated cryptographically under dedicated FIPS 140-3 Level 3 backed AWS KMS envelope keys using AES-256-GCM at rest and TLS 1.3 in transit across sovereign UK, EU, US, and UAE vaults, with optional Bring-Your-Own-Key (BYOK) custody. Access controls enforce federated SAML 2.0 / OIDC SSO, automated SCIM 2.0 lifecycle revocation, mandatory phishing-resistant FIDO2 MFA, imprint and Title-ID scoped RBAC, Zero Standing Privileges for cloud engineers, ephemeral rootless preflight sandboxes, immutable SIEM-streamed WORM audit logs, annual independent CREST-accredited penetration testing, and a contractual ≤ 24-hour security incident notification SLA. Security architecture packs, CAIQ v4 questionnaire responses, and sanitised penetration-test executive summaries are furnished promptly to prospective and subscribing enterprise CISO teams under mutual confidentiality via Security@BritishNoble.com.
1. ISMS Governance Charter & ISO 27001 / SOC 2 Control Mapping
British Noble operates a formal Information Security Management System reviewed semi-annually by the Executive Risk & Security Committee and directed day-to-day by the Chief Information Security Officer (Security@BritishNoble.com). Policies, cryptographic standards, access matrices, and business-continuity runbooks undergo mandatory annual re-certification and version-controlled audit logging.
To streamline procurement scrutiny by publishing group CISOs, university information-governance boards, and institutional auditors, our twelve technical control domains map directly against international assurance standards:
| British Noble Security Domain | ISO/IEC 27001:2022 Annex A | SOC 2 Trust Criteria | Primary Technical Enforcement |
|---|---|---|---|
| Cryptographic Key Isolation | A.8.24 Use of Cryptography | CC6.1, CC6.7, C1.1 | Per-tenant AWS KMS HSM envelope keys, AES-256-GCM, TLS 1.3 |
| Identity, SSO & Imprint RBAC | A.5.15, A.5.18, A.8.5 | CC6.2, CC6.3 | SAML 2.0, SCIM 2.0, WebAuthn MFA, PostgreSQL Row-Level Security |
| Ephemeral Compute & Network | A.8.20, A.8.22, A.8.23 | CC6.6, CC7.1 | Private VPCs, WAF/DDoS shields, rootless single-use preflight containers |
| Secure SDLC & CREST Testing | A.8.8, A.8.25, A.8.28, A.8.29 | CC8.1, CC7.1 | Signed commits, SAST/DAST/SBOM gates, annual CREST penetration tests |
| Immutable Logging & Breach SLA | A.8.15, A.8.16, A.5.24-A.5.28 | CC7.2, CC7.3, CC7.4 | WORM audit ledger, SIEM streaming, ≤ 24-hour controller notification |
| Resilience & KMS Erasure | A.8.13, A.8.14, A.8.10 | A1.1, A1.2, C1.2 | 3-AZ sync replication, 15m RPO / 2h RTO, NIST SP 800-88 crypto-shredding |
2. Cryptographic Standards & Per-Tenant HSM Key Hierarchy
Encryption in Transit: All external client connections, OpenAPI 3.1 calls, Connected Author Portal sessions, webhook dispatches, and internal service-to-service traffic require TLS 1.3 (or TLS 1.2 strictly restricted to ECDHE forward-secret cipher suites with AES-256-GCM or ChaCha20-Poly1305 where legacy retailer EDI gateways negotiate TLS 1.2). HTTP Strict Transport Security (HSTS) with includeSubDomains and preload is enforced across all domains, and outbound distribution channels utilise SSH-Ed25519 or RSA-4096 SFTP host-key pinning.
Encryption at Rest & Envelope Key Hierarchy: Zero customer manuscripts, proofs, partner credentials, tax forms, or database volumes are ever written to disk unencrypted. British Noble enforces a three-tier cryptographic envelope hierarchy backed by FIPS 140-3 Level 3 validated AWS Key Management Service (KMS) Hardware Security Modules within Customer's pinned cloud region: (1) a regional HSM Root Key; (2) a dedicated Per-Tenant Customer Master Key (CMK) logically isolated to a single publishing organisation via strict IAM key policies; and (3) unique 256-bit Per-Object Data Encryption Keys (DEKs) encrypting individual manuscript files, PDF/X-1a plates, EPUB masters, SFTP secrets, and W-8BEN/W-9 records under AES-256-GCM.
Tenant CMKs undergo automated cryptographic rotation every 365 days without downtime. Enterprise & Groups customers may optionally configure Bring Your Own Key (BYOK / External KMS), retaining unilateral ability to revoke key-grant permissions from their own AWS account.
3. Identity Federation, SCIM Lifecycle & Granular Imprint RBAC
British Noble supports enterprise single sign-on via SAML 2.0 and OpenID Connect (OIDC) across Okta, Microsoft Entra ID, Google Workspace, OneLogin, and Ping Identity, paired with SCIM 2.0 directory synchronisation so employee role changes or departures in Customer's HRIS/IdP revoke British Noble tokens instantaneously.
Where native authentication is utilised, passwords are hashed via memory-hard Argon2id with unique per-credential salts, checked automatically against compromised-credential k-anonymity corpora, and paired with mandatory multi-factor authentication (FIDO2/WebAuthn hardware passkeys or RFC 6238 TOTP). Modifying any royalty payee bank coordinate, tax withholding rate, or SFTP distribution endpoint triggers mandatory step-up MFA re-authentication and dual-custody finance approval.
Inside multi-imprint publishing groups, Role-Based Access Control (RBAC) enforces least privilege across four hierarchical dimensions: Group Entity → Imprint → Departmental Capability → Individual Title ID, backed at the database layer by PostgreSQL Row-Level Security (RLS) policies so external freelance copyeditors or jacket designers see solely the specific ISBNs assigned to them and never view acquisition advances or group-wide ledgers.
4. VPC Segmentation, WAF Defence & Ephemeral Preflight Sandboxes
Production environments run inside dedicated, regionally isolated Virtual Private Clouds (VPCs) segmented into public ingress load-balancer tiers, private stateless application tiers, and air-gapped private persistence subnets lacking public IPv4/IPv6 addresses or direct internet gateways. Ingress traffic traverses enterprise Web Application Firewalls (WAF) enforcing OWASP Core Rule Sets, bot-anomaly mitigation, adaptive per-tenant API rate limiting, and volumetric L3/L4/L7 DDoS scrubbing.
Because publishing operations ingest complex binary and XML files uploaded by external contributors (Word .docx manuscripts, Adobe .idml archives, embedded OpenType fonts, high-resolution TIFF/JPEG plates, and EPUB zip containers), British Noble never parses untrusted files inside shared application memory. Every preflight, typesetting, and ONIX transformation job executes inside an ephemeral, rootless, read-only Linux micro-container with dropped kernel capabilities (seccomp / AppArmor), zero outbound internet egress, strict CPU/memory quotas, and immediate container destruction the millisecond validation completes.
5. Secure Software Development Lifecycle & SBOM Governance
All platform source code and Infrastructure-as-Code (Terraform) templates reside in access-controlled repositories enforcing GPG/SSH cryptographically signed commits and protected main branches. Every pull request requires: (a) peer review and approval by at least one senior staff engineer who did not author the change; (b) automated Static Application Security Testing (SAST) and secret-leak scanning; (c) Software Composition Analysis (SCA) generating CycloneDX Software Bills of Materials (SBOMs) and blocking builds containing known exploitable CVEs; and (d) Dynamic Application Security Testing (DAST) and multi-tenant RLS isolation regression suites in staging.
Development, staging, sandbox, and production environments are strictly separated across distinct cloud accounts, VPCs, and KMS domains. Production customer manuscripts, contributor PII, and financial ledgers are never copied into development or QA environments; engineering tests execute exclusively against synthetic bibliographic fixtures.
6. Annual CREST Penetration Testing & Vulnerability SLAs
In addition to continuous automated vulnerability scanning across container images, operating-system packages, and TLS endpoints, British Noble commissions comprehensive independent grey-box and black-box penetration tests at least once every twelve (12) months (and prior to major architectural subsystem launches) conducted exclusively by CREST-accredited external offensive-security consultancies.
Penetration testing engagements specifically target multi-tenant KMS/RLS boundary isolation, SAML/OIDC authentication flows, XML External Entity (XXE) and SSRF vectors in ONIX/IDML/EPUB parsers, Connected Author Portal privilege boundaries, and royalty rounding/payout logic. Identified vulnerabilities across internal scans, CREST engagements, or our Coordinated Vulnerability Disclosure Policy adhere to binding remediation SLAs based on CVSS v4.0 severity: Critical (9.0-10.0) ≤ 72 hours; High (7.0-8.9) ≤ 14 calendar days; Medium (4.0-6.9) ≤ 30 calendar days; and Low (0.1-3.9) ≤ 90 calendar days. Executive attestation letters summarising scope, methodology, and verified zero open Critical/High findings are shared with enterprise customers under NDA.
7. Tamper-Evident Audit Logging & Enterprise SIEM Streaming
Every security-relevant action inside a tenant workspace generates a structured JSON audit record signed with a chained SHA-256 hash digest and written to append-only Write-Once-Read-Many (WORM) storage. Logged events include all user sign-ins and failed authentication attempts, RBAC permission grants, AI kill-switch toggles, manuscript and galley downloads, contract term edits, ONIX 3.1.2 channel dispatches, tax form uploads, and payee bank modifications.
Audit records capture UTC microsecond timestamps, actor user ID, federated session ID, source IP and ASN, target Title ID/ISBN, action verb, and before/after state metadata without logging raw cleartext passwords or unmasked bank account numbers. Enterprise & Groups customers can query twelve months of hot audit history in-app or stream real-time events via TLS webhook or AWS EventBridge directly into Splunk, Datadog, Microsoft Sentinel, CrowdStrike Falcon LogScale, or Sumo Logic.
8. Workforce Security, Endpoint Hardening & Zero Standing Access
All British Noble personnel undergo pre-employment identity, right-to-work, reference, and criminal/credit background verification as permitted by local statute, sign binding intellectual-property and manuscript confidentiality deeds, and complete semi-annual role-specific security engineering training alongside simulated social-engineering exercises.
Corporate workstations are centrally provisioned via Mobile Device Management (MDM) enforcing full-disk encryption (FileVault 2 / BitLocker), automatic screen locks, disabled removable USB storage, OS patch SLAs within 7 days, hardware FIDO2 YubiKeys, and 24/7 Endpoint Detection and Response (EDR) sensors. Engineers hold Zero Standing Privileges (ZSP) to production databases or KMS vaults; break-glass operational access requires a ticket-linked, peer-approved Just-in-Time (JIT) elevation grant expiring automatically within sixty (60) minutes with full session command recording.
9. 24/7 Security Operations & <= 24-Hour Breach Notification
British Noble's Security Operations team monitors infrastructure, WAF, EDR, and cross-tenant anomaly telemetry 24/7/365. Automated behavioural tripwires immediately alert on-call security engineers upon detecting anomalous bulk manuscript downloads, impossible-travel session anomalies, repeated RLS policy rejections, or unexpected container syscalls.
Our documented Incident Response Plan follows NIST SP 800-61 Rev. 2 phases: Preparation, Detection & Analysis, Containment & Eradication, Recovery, and Blameless Post-Incident Review, tested semi-annually via tabletop simulations involving the CISO, DPO, VP of Infrastructure, and Legal Counsel. Where any confirmed security incident results in unauthorised access to, acquisition of, or disclosure of Customer Content or Controller Personal Data, British Noble notifies affected enterprise customers within twenty-four (≤ 24) hours of confirmation, furnishing forensic indicators, affected ISBN/record inventories, and containment actions.
10. WORM Backup Immutability, Physical Data Centres & Continuity
Underlying physical data centres operated by Amazon Web Services across London, Frankfurt, Virginia, and Dubai enforce biometric mantraps, 24/7 armed or badged perimeter security, CCTV retention, redundant N+1 UPS battery arrays, diesel generators, and ISO 27001 / SOC 2 Type II physical attestations. Zero customer data is ever stored on physical servers inside British Noble corporate offices.
Encrypted database snapshots and object-version archives are written continuously to secondary availability zones under AWS Backup Vault Lock (WORM governance mode), preventing even a compromised root administrator credential from deleting or encrypting backup archives during a ransomware scenario, guaranteeing our contractual 15-minute RPO and 2-hour RTO.
11. Third-Party & Fourth-Party Supply Chain Risk Management
No external software vendor or infrastructure sub-processor is integrated into production data paths without passing formal CISO and DPO vendor security due diligence, verifying SOC 2 Type II / ISO 27001 certifications, encryption standards, zero-AI-training contractual covenants, vulnerability disclosure maturity, and fourth-party concentration risk. Critical Tier 1 vendors undergo mandatory annual security re-assessment, and all integration API tokens operate under narrowly scoped OAuth or IAM permissions with automated secret rotation.
12. Enhanced Pre-Publication Embargo Controls for High-Risk Titles
For investigative journalism, central-bank economic reports, geopolitical memoirs, and major literary prize frontlists subject to strict global on-sale embargoes, British Noble provides dedicated High-Security Embargo Mode per Single Title Record. When activated by a publishing director, Embargo Mode: (a) masks the real working title and author name behind a random internal codename across general production schedules and preflight queues; (b) restricts manuscript and proof visibility to an explicit named-user allowlist; (c) embeds forensic, recipient-specific visible and invisible watermarks on every downloaded digital review galley; and (d) holds outbound ONIX 3.1.2 metadata blocks in encrypted staging until the exact publisher-approved metadata release date.
Multi-Jurisdiction Governance
Aligned with UK GDPR, Data Protection Act 2018, EU SCCs, CCPA/CPRA, UAE Federal Decree-Law No. 45 of 2021 (PDPL), ISO/IEC 27001:2022, and SOC 2 Type II.
Zero Manuscript Training
Customer manuscripts, proof files, ONIX records, and royalty ledgers are isolated per tenant and never used to train foundation or shared models.
Information Security & CISO Desk
Enterprise procurement teams may request countersigned schedules, DPA exhibits, and audit certificates directly.
Security@BritishNoble.com →