/security

IPAD Security Model

User Input

$ARGUMENTS

Instructions

Note: The ipad-context hook automatically injects project context (project list, existing artifacts, maturity level) into this command's execution. Use that context to identify the target project directory, project ID, and any existing artifacts.

Step 0: Prerequisite Check

1. Identify the target project from $ARGUMENTS (the project ID, e.g., 001).
2. Verify that an Entity Model artifact (IPAD-{PROJECT_ID}-ENTM-*.md) exists in the project directory. This is a mandatory prerequisite.
3. If the ENTM artifact is missing, stop and inform the user:
   • Explain that the security model requires the entity model to define data assets that need protection.
   • Suggest running /ipad-kit:entity-model first.
4. Check for and read optional prerequisite artifacts if they exist:
   • Assessment (IPAD-{PROJECT_ID}-ASSESS-*.md) — for maturity context
   • Data Classification (IPAD-{PROJECT_ID}-DCLS-*.md) — for classification tiers to align security controls
   • Governance (IPAD-{PROJECT_ID}-GOVR-*.md) — for governance structure integration

Step 1: Read Template

1. Check for a local template override at .ipad/templates/security-template.md.
2. If the local override does not exist, read the default template at ${CLAUDE_PLUGIN_ROOT}/templates/security-template.md.
3. If neither template exists, proceed using the built-in structure defined in these instructions.

Step 2: Read Reference Data

1. Read ${CLAUDE_PLUGIN_ROOT}/references/framework/governance/ica-security.md — the ICA security model (Integrity, Confidentiality, Accessibility).
2. Read the entity model artifact to identify data assets requiring security controls.
3. If a data classification artifact exists, read it to map security controls to classification tiers.
4. Read ${CLAUDE_PLUGIN_ROOT}/references/framework/governance/roles-and-responsibilities.md — security-related role responsibilities.
5. Read ${CLAUDE_PLUGIN_ROOT}/references/principles.md — security-relevant principles.

Step 3: Gather Regulatory Context (Optional)

1. If the IPA's jurisdiction is known, consider invoking the ipad-regulatory-research agent to retrieve jurisdiction-specific security and data protection requirements.
2. If the agent is not available or the user declines, use general best-practice security guidance and note that jurisdiction-specific requirements should be validated.

Step 4: Generate Security Model

Produce the following sections in the output artifact:

4.1 Document Information

Auto-populate the following fields at the top of the document:

• Document ID: IPAD-{PROJECT_ID}-SECR-v1.0
• Project: {project name from context}
• Date: {current date}
• Status: Draft
• Prerequisites Used: List the ENTM, ASSESS, DCLS, GOVR, and any other artifacts read

4.2 ICA Security Model

Define the three-pillar security architecture:

• Integrity: Asset inventory and data lineage, hash verification and checksums, immutable audit logs, digital signatures for data contracts, tamper detection and alerting
• Confidentiality: Classification-based access control, encryption standards (at rest and in transit), data masking and anonymisation, secure data sharing protocols, privacy-enhancing technologies
• Accessibility: Availability SLAs per classification tier, disaster recovery and business continuity, access provisioning and deprovisioning workflows, self-service data discovery (within authorisation boundaries)

4.3 Security Architecture by Layer

Define security controls specific to each IPAD Framework layer (1-8):

• Layer 1 (Global FDI Drivers): Source authentication, data provenance verification
• Layer 2 (IPA Raw Sources): Ingestion security, API authentication, file integrity checks
• Layer 3 (Data Fabric): Pipeline encryption, integration security, metadata access control
• Layer 4 (Curated Data Stores): Database security, row/column-level access, data masking
• Layer 5 (Analytics & Insights): Model security, output classification, result anonymisation
• Layer 6 (Insight Delivery): Channel security, report access control, API authorisation
• Layer 7 (Decision Support): Decision audit trails, executive access management
• Layer 8 (User Applications): Application security, session management, UI-level access control

4.4 Access Control Model

• RBAC (Role-Based Access Control) structure aligned with governance roles
• ABAC (Attribute-Based Access Control) for classification-based access decisions
• Least privilege principle implementation
• Access request and approval workflows
• Periodic access review cadence per classification tier
• Emergency and break-glass access procedures

4.5 Encryption Strategy

• Encryption at rest: Standards (AES-256 minimum for Confidential+), key management, storage encryption
• Encryption in transit: TLS requirements, certificate management, API security
• Key management: Key lifecycle, rotation schedules, HSM requirements
• Tokenisation: When and how to tokenise sensitive investor data
• End-to-end encryption for cross-border data transfers

4.6 Cross-Border Security

• Data sovereignty requirements per jurisdiction
• Data transfer mechanisms (adequacy decisions, SCCs, BCRs)
• Data localisation requirements and implementation
• International data sharing security controls
• Jurisdiction risk assessment for data storage locations

4.7 Incident Response

• Detection: Security monitoring, SIEM integration, anomaly detection
• Containment: Isolation procedures, access revocation, communication protocols
• Recovery: Data restoration, system rebuilding, integrity verification
• Reporting: Regulatory notification requirements, stakeholder communication, post-incident review
• Incident severity classification and response SLAs

4.8 Security Metrics and KPIs

• Security posture monitoring KPIs (mean time to detect, mean time to respond)
• Access control effectiveness metrics
• Encryption coverage metrics
• Vulnerability management metrics
• Compliance audit results tracking
• Security maturity score aligned with IPAD maturity levels

Step 5: Write Output

1. Write the completed artifact to projects/{project-dir}/IPAD-{PROJECT_ID}-SECR-v1.0.md.
2. Append the generation metadata footer:

---
**Generated by**: IPAD Kit `/ipad-kit:security` command
**Generated on**: {DATE}
**IPAD Kit Version**: {IPAD_KIT_VERSION}
**Project**: {PROJECT_ID}-{project-name}

Step 6: Present Summary and Next Steps

1. Confirm the artifact was written successfully.
2. Highlight key security findings: highest-risk data assets, critical access control gaps, encryption coverage.
3. Recommend next commands:
   • /ipad-kit:data-classification — Review or define data classification for security alignment
   • /ipad-kit:governance — Update governance framework with security control integration