/**
 * NCSC Guidelines for Secure AI System Development Compliance Pack
 *
 * Framework:
 *   NCSC (National Cyber Security Centre, UK) — "Guidelines for secure AI
 *   system development" (2024), co-authored with CISA (US), ACSC (AU),
 *   CCCS (CA), BSI (DE), ANSSI (FR) and 11 further international partners.
 *   Not legally binding legislation but referenced by UK public-sector
 *   procurement (Crown Commercial Service frameworks, Cyber Essentials Plus
 *   supplier tiers) and incorporated by reference into Cabinet Office
 *   AI procurement guidance.
 *
 *   The guidelines are structured across four sequential phases that mirror
 *   an AI system's lifecycle:
 *     Phase 1 — Secure design
 *       (threat modelling, supply-chain risk, attack-surface minimisation)
 *     Phase 2 — Secure development
 *       (dependency integrity, model provenance, secure coding for AI)
 *     Phase 3 — Secure deployment
 *       (infrastructure hardening, access controls, deployment records)
 *     Phase 4 — Secure operation and maintenance
 *       (monitoring, incident response, vulnerability disclosure, red-teaming)
 *
 * Jurisdiction: GB (United Kingdom)
 * Authority: NCSC (National Cyber Security Centre, part of GCHQ)
 *   Joint with: CISA, ACSC, CCCS, BSI, ANSSI + 11 international partners.
 *   UK procurement references: Crown Commercial Service, Cabinet Office,
 *   Cyber Essentials Plus supplier requirements.
 *
 * Relation to other packs:
 *   - Pairs with `cyber-essentials` (foundational UK cyber hygiene baseline)
 *   - Pairs with `ncsc-caf` (heavier outcome-based assessment for CNI operators)
 *   - Pairs with `uk-ai-framework` (UK crossgov AI principles)
 *   - Distinct from ISO 42001 (management-system certification) — this pack
 *     focuses on engineering-phase secure-by-design controls for AI, not on
 *     the management system layer.
 *
 * Why this pack:
 *   - Crown Commercial Service and GDS increasingly require suppliers to
 *     evidence adherence to these guidelines for AI system procurement.
 *   - The supply-chain and model-provenance requirements have direct
 *     enforcement hooks (AI_SUPPLY_CHAIN_RISK, AI_THREAT_MODEL elements).
 *   - Red team findings and vulnerability reports (MODEL_VULNERABILITY_REPORT,
 *     RED_TEAM_FINDING) are increasingly mandated as pre-procurement evidence.
 *   - AI-specific incident response distinguishes this pack from generic
 *     incident-response frameworks.
 *
 * Retention: 7 years — aligned with public-sector procurement record-keeping
 *   standards (Cabinet Office guidance) and NCSC recommended evidence
 *   retention for AI security assessments.
 *
 * Source citation: NCSC Guidelines for secure AI system development (2024),
 *   National Cyber Security Centre. Crown copyright; freely distributable.
 *
 * @connexum/ai-governance
 */
import { CompliancePack } from './index';
import { CategoryClassifiers } from '../classification/pack-driven-classifier';
/**
 * NCSC AI Security category classifiers.
 *
 * Each classifier targets a distinct data element from the four phases
 * of the NCSC Guidelines for secure AI system development (2024).
 */
export declare const NCSC_AI_SECURITY_CATEGORY_CLASSIFIERS: CategoryClassifiers;
export declare const NCSC_AI_SECURITY_PACK: CompliancePack & {
    categoryClassifiers: CategoryClassifiers;
};
//# sourceMappingURL=ncsc-ai-security.d.ts.map