INFORMATION SECURITY AND COMPLIANCE PLAN
tasleemat asset PMO-04.13.01 template --lang en
Deliverable Summary & Governance Boundaries
Lifecycle Phase Alignment
Phase 04: Planning
Sizing Tier Requirements
Validation Contract
This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.
tasleemat validate PMO-04.13.01 ./completed_data.json
Template Markdown (Bilingual)
<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context. -->
<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">INFORMATION SECURITY AND COMPLIANCE PLAN</h1>
| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |
---
## 1. Compliance Governance & Data Classification
**Regulatory Framework and Applicable Standards:**
[ Add details... ]
**Data Classification and Privacy Tiering:**
[ Add details... ]
---
## 2. Security Architecture & Incident Management
**Technical and Administrative Security Controls:**
[ Add details... ]
**Security Assessment and Penetration Testing Cadence:**
[ Add details... ]
---
## 3. Audit Governance & Sign-off Roles
**Incident Response Protocol and Breach Notification:**
[ Add details... ]
**Compliance Audit Gateways and Signoff Criteria:**
[ Add details... ]
---
### Sign-off and Approvals
| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Lead Reviewer / Architect** | {{Lead_Reviewer_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor / Owner** | {{Project_Sponsor_Name}} | _______________________ | [ .... - .... - .... ] |
---
<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
<span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
<strong>Template:</strong> INFORMATION SECURITY AND COMPLIANCE PLAN | <strong>Ref:</strong> PMO-04.13.01 <br>
<i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>
User Guide & Practitioner Instructions
Tasleemat Forms Guide
Project Artifact: Information Security and Compliance Plan
Document Reference:
This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Information Security and Compliance Plan in alignment with the Tasleemat framework.
1. What?
A standardized PMO deliverable (PMO-04.13.01) establishing information security and compliance plan protocols and governance baselines.
2. Why?
Ensures rigorous operational alignment, transparent stakeholder visibility, and structured project governance for information security and compliance plan.
3. When?
Maintained throughout project execution and updated during scheduled reviews or milestone transitions.
4. Who?
Authored by the Project Manager or designated lead; reviewed and approved by Project Sponsors and Governance Committees.
Tailoring Tips
- For small/agile teams, integrate into lightweight digital boards or automated reporting webhooks.
- For large/enterprise programs, mandate formal document control and signed executive stage-gate signoffs.
Alignment & Dependencies
1. Pre-requisites & Inputs (Upstream Dependencies)
- Mandatory: Project Charter (PMO-03.01), Risk Management Plan (PMO-04.08.01)
- Optional / Contextual: Data Privacy and Ethics Assessment (PMO-02.06)
2. Downstream Dependents
- Mandatory: Deliverable Technical Inspection Checklist (PMO-05.15)
- Optional / Contextual: Transition to Operations Checklist (PMO-07.04)
5. How?
To accurately and professionally complete the Information Security and Compliance Plan, populate all required sections based on project context:
- Regulatory Framework and Applicable Standards: Mandatory national regulations (NCA ECC, NDMO, GDPR, ISO 27001) governing project delivery.
- Data Classification and Privacy Tiering: Information classification scheme (Public, Internal, Confidential, Highly Confidential) and PII protections.
- Technical and Administrative Security Controls: Encryption at rest/in transit, identity and access management (IAM), multi-factor authentication, and audit trails.
- Security Assessment and Penetration Testing Cadence: Vulnerability scanning, automated code analysis (SAST/DAST), and third-party penetration testing gateways.
- Incident Response Protocol and Breach Notification: Escalation procedure, root cause containment, and mandatory regulatory reporting timeframes.
- Compliance Audit Gateways and Signoff Criteria: Stage-gate evidence packages required by Chief Information Security Officer (CISO) and legal counsel.
6. Reference Example
A fully completed, gold-standard reference example illustrating this artifact in practice is available:
๐ Completed Example: 04_13_01_Information_Security_and_Compliance_Plan_Example.md
LLM Generation Prompt & Agent Instructions
Information Security and Compliance Plan - Generation Prompt
System Instructions: This document contains instructions for generating the ยซInformation Security and Compliance Planยป. When asked to fill this template, follow the section-by-section instructions below. Refer to for project variables.
Context and Definition: A standardized PMO governance deliverable (PMO-04.13.01) for information security and compliance plan in compliance with PMI PMBOKยฎ standards.
Alignment & Dependencies: * Pre-requisites (Inputs): Project Charter (PMO-03.01), Risk Management Plan (PMO-04.08.01) * Downstream Dependents: Deliverable Technical Inspection Checklist (PMO-05.15)
Compliance Governance & Data Classification
Regulatory Framework and Applicable Standards
Instruction: Mandatory national regulations (NCA ECC, NDMO, GDPR, ISO 27001) governing project delivery.
Generated Value: [ Add details... ]
Data Classification and Privacy Tiering
Instruction: Information classification scheme (Public, Internal, Confidential, Highly Confidential) and PII protections.
Generated Value: [ Add details... ]
Security Architecture & Incident Management
Technical and Administrative Security Controls
Instruction: Encryption at rest/in transit, identity and access management (IAM), multi-factor authentication, and audit trails.
Generated Value: [ Add details... ]
Security Assessment and Penetration Testing Cadence
Instruction: Vulnerability scanning, automated code analysis (SAST/DAST), and third-party penetration testing gateways.
Generated Value: [ Add details... ]
Audit Governance & Sign-off Roles
Incident Response Protocol and Breach Notification
Instruction: Escalation procedure, root cause containment, and mandatory regulatory reporting timeframes.
Generated Value: [ Add details... ]
Compliance Audit Gateways and Signoff Criteria
Instruction: Stage-gate evidence packages required by Chief Information Security Officer (CISO) and legal counsel.
Generated Value: [ Add details... ]
Information Security and Compliance Plan (Reference Example)
๐ Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (). All company names, project references, and figures are realistic fictional simulations.
Apex Global Solutions
Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01
INFORMATION SECURITY AND COMPLIANCE PLAN
1. Compliance Governance & Data Classification
Regulatory Framework and Applicable Standards: Apex Enterprise Baseline: Verified operational compliance for regulatory framework and applicable standards. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
Data Classification and Privacy Tiering: Apex Enterprise Baseline: Verified operational compliance for data classification and privacy tiering. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
2. Security Architecture & Incident Management
Technical and Administrative Security Controls: Apex Enterprise Baseline: Verified operational compliance for technical and administrative security controls. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
Security Assessment and Penetration Testing Cadence: Apex Enterprise Baseline: Verified operational compliance for security assessment and penetration testing cadence. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
3. Audit Governance & Sign-off Roles
Incident Response Protocol and Breach Notification: Apex Enterprise Baseline: Verified operational compliance for incident response protocol and breach notification. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
Compliance Audit Gateways and Signoff Criteria: Apex Enterprise Baseline: Verified operational compliance for compliance audit gateways and signoff criteria. Detailed analysis, SLA criteria, and execution metrics have been comprehensively documented and aligned with PMO delivery governance standards.
Sign-off and Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Project Manager | Faisal Al-Harbi, PMP | Faisal Al-Harbi | 2026-03-16 |
| Lead Reviewer / Architect | Dr. Tariq Al-Mansoor | T. Al-Mansoor | 2026-03-17 |
| Project Sponsor / Owner | Sarah Al-Ghamdi (VP Operations) | Sarah Al-Ghamdi | 2026-03-18 |
Verified Production Reference, by Tasleemat
Draft 2020-12 JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://tasleemat.pmo/schemas/completed/PMO-04.13.01.schema.json",
"title": "Completed INFORMATION SECURITY AND COMPLIANCE PLAN Data Contract",
"description": "Additive structural schema validating completed INFORMATION SECURITY AND COMPLIANCE PLAN artifact data payloads (PMO-04.13.01).",
"type": "object",
"properties": {
"artifact_id": {
"type": "string",
"const": "PMO-04.13.01"
},
"metadata": {
"type": "object",
"properties": {
"project_name": {
"type": "string",
"minLength": 1
},
"project_code": {
"type": "string"
},
"date_prepared": {
"type": "string",
"format": "date"
},
"project_manager": {
"type": "string",
"minLength": 1
},
"prepared_by": {
"type": "string",
"minLength": 1
},
"version": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"draft",
"baselined",
"in_review",
"approved"
]
}
},
"required": [
"project_name",
"date_prepared",
"project_manager",
"prepared_by"
]
},
"compliance_governance_data_classification": {
"type": "object",
"properties": {
"regulatory_framework_and_applicable_standards": {
"type": "string",
"minLength": 1,
"description": "Mandatory national regulations (NCA ECC, NDMO, GDPR, ISO 27001) governing project delivery."
},
"data_classification_and_privacy_tiering": {
"type": "string",
"minLength": 1,
"description": "Information classification scheme (Public, Internal, Confidential, Highly Confidential) and PII protections."
}
},
"required": [
"regulatory_framework_and_applicable_standards",
"data_classification_and_privacy_tiering"
]
},
"security_architecture_incident_management": {
"type": "object",
"properties": {
"technical_and_administrative_security_controls": {
"type": "string",
"minLength": 1,
"description": "Encryption at rest/in transit, identity and access management (IAM), multi-factor authentication, and audit trails."
},
"security_assessment_and_penetration_testing_cadence": {
"type": "string",
"minLength": 1,
"description": "Vulnerability scanning, automated code analysis (SAST/DAST), and third-party penetration testing gateways."
}
},
"required": [
"technical_and_administrative_security_controls",
"security_assessment_and_penetration_testing_cadence"
]
},
"audit_governance_sign_off_roles": {
"type": "object",
"properties": {
"incident_response_protocol_and_breach_notification": {
"type": "string",
"minLength": 1,
"description": "Escalation procedure, root cause containment, and mandatory regulatory reporting timeframes."
},
"compliance_audit_gateways_and_signoff_criteria": {
"type": "string",
"minLength": 1,
"description": "Stage-gate evidence packages required by Chief Information Security Officer (CISO) and legal counsel."
}
},
"required": [
"incident_response_protocol_and_breach_notification",
"compliance_audit_gateways_and_signoff_criteria"
]
}
},
"required": [
"artifact_id",
"metadata",
"compliance_governance_data_classification",
"security_architecture_incident_management",
"audit_governance_sign_off_roles"
]
}
๐ Form Field Definitions Dictionary (Legacy Specification)
{
"form_name": "INFORMATION SECURITY AND COMPLIANCE PLAN",
"document_reference": "PMO-04.13.01",
"_llm_instructions": "Populate the fields of 'INFORMATION SECURITY AND COMPLIANCE PLAN' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.13.01.",
"project_title": "",
"date_prepared": "",
"fields": {
"f01_Regulatory_Framework_and_Applicable_Standards": {
"section": "Compliance Governance & Data Classification",
"label": "Regulatory Framework and Applicable Standards",
"guidance": "Mandatory national regulations (NCA ECC, NDMO, GDPR, ISO 27001) governing project delivery.",
"value": ""
},
"f02_Data_Classification_and_Privacy_Tiering": {
"section": "Compliance Governance & Data Classification",
"label": "Data Classification and Privacy Tiering",
"guidance": "Information classification scheme (Public, Internal, Confidential, Highly Confidential) and PII protections.",
"value": ""
},
"f03_Technical_and_Administrative_Security_Controls": {
"section": "Security Architecture & Incident Management",
"label": "Technical and Administrative Security Controls",
"guidance": "Encryption at rest/in transit, identity and access management (IAM), multi-factor authentication, and audit trails.",
"value": ""
},
"f04_Security_Assessment_and_Penetration_Testing_Cadence": {
"section": "Security Architecture & Incident Management",
"label": "Security Assessment and Penetration Testing Cadence",
"guidance": "Vulnerability scanning, automated code analysis (SAST/DAST), and third-party penetration testing gateways.",
"value": ""
},
"f05_Incident_Response_Protocol_and_Breach_Notification": {
"section": "Audit Governance & Sign-off Roles",
"label": "Incident Response Protocol and Breach Notification",
"guidance": "Escalation procedure, root cause containment, and mandatory regulatory reporting timeframes.",
"value": ""
},
"f06_Compliance_Audit_Gateways_and_Signoff_Criteria": {
"section": "Audit Governance & Sign-off Roles",
"label": "Compliance Audit Gateways and Signoff Criteria",
"guidance": "Stage-gate evidence packages required by Chief Information Security Officer (CISO) and legal counsel.",
"value": ""
}
}
}