CIP DOCUMENTS

CIP documentation

• CIP Documents
  • Management policy
  • License
  • Guide
• CIP (Civil Infrastructure Platform) Glossary
  • References

process

• CIP Development process (SM-1)
  • 1. Introduction
  • 2. Scope
  • 3. SM-1 : Development process
• CIP Requirements
  • Introduction
  • Process of defining CIP Requirements
  • CIP Functional Requirements
  • CIP Non-Functional Requirements
  • CIP Security Requirements
• Secure Design principles (SD-1)
  • Introduction
  • Scope
  • SD-1 : Secure Design principles
• Configuration Management
  • 1. Objective
  • 2. Acronyms
  • 3. Content
  • 4. CIP Kernel version
  • 5. CIP Core version
  • 6. CIP Core change control
  • 7. CIP kernel change control
  • 8. Audit Logging
• CIP CVE handling
  • 1. Objective
  • 2. Scope
  • 3. CIP Core CVE Handling
  • 4. CIP Kernel CVE Handling
  • 5. References
• Traceability from CIP requirements to design and testing
  • Introduction
  • Acronyms
  • Process behind creating requirement traceability matrices
  • Traceability matrix from CIP requirements to design
  • Traceability matrix from CIP requirements to testing process
• Management of security issues in CIP
  • Description
  • Objective
  • Scope
  • DM-1: Receiving notifications of security-related issues
  • DM-2: Reviewing security-related issues
  • DM-3: Assessing security-related issues
  • DM-4: Addressing security-related issues
  • DM-5: Disclosing security-related issues
  • DM-6: Periodic review of security defect management practice
• CIP File Integrity
  • 1. Objective
  • 2. Scope
  • 3. File Integrity of Source Code
  • 4. File Integrity of Images
  • 5. References
• Roles and Responsibilities
  • 1. Objective
  • 2. Scope
  • 4. Roles
  • 5. RACI
  • 6. Roles and Responsibilities
• CIP Release Security Checklist
  • 1. Objective
  • 2. Scope
  • 3. Checklist Usage
  • 4. Checklist
• Roles and Responsibilities
  • 1. Objective
  • 2. Scope
  • 3. Review and Approval Process
• Security Design review and best practices in CIP
  • Introduction
  • Scope
  • SD-3 : Security Design review
  • SD-4 : Secure Design best practices
• CIP Secure Development Process
  • 1. Overview
  • 2. [SM-1] Secure Development Process
  • 3. [SM-2] Identification of Responsibilities
  • 4. [SM-3] CIP Software version
  • 5 [SM-4] CIP Developer Security Expertise
  • 6 [SM-5] Process Scoping
  • 7. [SM-6] File Integrity
  • 8. [SM-7] Development Environment Security
  • 9. [SM-8] Private Key Protection
  • 10. [SM-9] Security Risk analysis for externally provided components
  • 11. [SM-10] Custom Developed Components from third party
  • 12. [SM-11] Security Issues Assessment
  • 13. [SM-12] Documented Checklist Review
  • 14. [SM-13] Define Review frequency
  • 15. [SR-1, SR-3, SR-4] Product Security Context
  • 16. [SR-2] Threat Model
  • 17. [SR-5] Security Requirements Review and Approval
  • 18. [SD-1] Secure Design Principles
  • 19. [SD-2] Defense in depth design
  • 20. [SD-3, SD-4] Security design review
  • 21. [SI-1] Security implementation review
  • 22. [SI-2] Secure Coding Standards
  • 23. [SVV-1] Security requirement testing
  • 24. [SVV-2] Threat Mitigation testing
  • 25. [SVV-3] Vulnerability testing
  • 26. [SVV-4] Penetration testing
  • 27. [SVV-5] Independence of testers
  • 28. [DM-1 to DM-5] Receiving notifications of security issues
  • 29. [DM-6] Periodic review of security defect management practice
  • 30. [SUM-1] Security Update Qualification
  • 31. [SUM-2, SUM-3] Security update documentation
  • 32. [SUM-4] Security update delivery
  • 33. [SUM-5] Timely delivery of security patches
  • 34. [SG-1, SG-2] Product defense in depth
  • 35. [SG-3] Security Hardening guidelines
  • 36. [SG-4] Secure Disposal Guidelines
  • 37. [SG-5] Secure operation guidelines
  • 38. [SG-6] Account management guidelines
  • 39. [SG-7] Documentation Review
• CIP Testing
  • 1. Introduction
  • 2. Objective
  • 3. Scope
  • 4. CIP Kernel testing
  • 5. CIP Core Testing
• Use of Cryptography
  • 1. Objective
  • 2. Use of Cryptography Requirement CR-4.3
  • 3. Recommended NIST Standards
  • 4. OpenSSL Support for FIPS-140-2
  • 5. Guidelines for CIP Users
  • 6. CIP Review frequency

iec-62443-assessment

• CIP IEC-62443-4-2 CIP Essential function and verification details
  • 1. Overview
  • 2. CIP essential function
  • 3. Verification of essential function
• CIP IEC-62443-4-2 Foundational Requirement-1 Assessment details
  • 1. Overview
  • 2. CR-1.1 Human user identification and authentication [Met]
  • 3. CR-1.1 RE(1) Unique identification and authentication [Met]
  • 4. CR-1.1 RE(2) Multifactor authentication for all interfaces [NA]
  • 5. CR-1.2 Software process and device identification and authentication [NA]
  • 6. CR-1.3 Account Management [Met]
  • 7. CR-1.4 Identifier management [Met]
  • 8. CR-1.5 Authenticator management [Met]
  • 9. CR-1.6, NDR-1.6 Wireless access management & NDR-1.6 RE(1) Unique identification and authentication [NA]
  • 10. CR-1.7 Strength of password-based authentication [Met]
  • 11. CR-1.8 Public key infrastructure certificates [Met]
  • 12. CR-1.9 Strength of public key-based authentication [Met]
  • 13. CR-1.9 RE(1) Hardware security for public key-based authentication [NA]
  • 14. CR-1.10 Authenticator feedback [Met]
  • 15. CR-1.11 Unsuccessful login attempts [Met]
  • 16. CR-1.12 System use notification [NA]
  • 17. CR-1.13 Access via untrusted networks [NA]
  • 18. NDR-1.13 Access via untrusted networks [NA]
  • 19. NDR-1.13 RE(1) Explicit access request approval [NA]
  • 20. CR-1.14 Strength of symmetric key-based authentication [NA]
  • References
• CIP IEC-62443-4-2 Foundational Requirement-3 Assessment details
  • 1. Overview
  • 2. CR-3.1 Communication integrity [Met]
  • 3. CR-3.1 RE(1) Communication authentication [Met]
  • 4. CR-3.2 Protection from malicious code [NA]
  • 5. EDR 3.2, HDR 3.2, NDR 3.2, SAR 3.2 Protection from malicious code [NA]
  • 6. HDR-3.2 Report version of code protection [NA]
  • 7. CR-3.3 & CR-3.3 RE (1) Security functionality verification [NA]
  • 8. CR-3.4 Software and information integrity [Met]
  • 9. CR-3.4 RE(1) Authenticity of software and information [Met]
  • 10. CR-3.4 RE(2) Automated notification of integrity violations [NA]
  • 11. CR-3.5 Input validation [Met]
  • 12. CR-3.6 Deterministic output [NA]
  • 13. CR-3.7 Error handling [Met]
  • 14. CR-3.8 Session integrity [Met]
  • 15. CR-3.9 Protection of audit information [Met]
  • 16. CR-3.9 RE(1) Audit records on write-once media [NA]
  • 17 EDR-3.10, NDR-3.10 Support for updates [Met]
  • 18 HDR-3.10 Support for updates [NA]
  • 19. EDR-3.10 RE(1), NDR-3.10 RE(1) Update authenticity and integrity [Met]
  • 20. HDR-3.10 RE(1) Update authenticity and integrity
  • 21. CR-3.11, EDR 3.11, HDR 3.11, NDR 3.11 Physical tamper resistance and detection [NA]
  • 22. EDR 3.11 RE(1), HDR 3.11 RE(1), NDR 3.11 RE(1) Notification of a tampering attempt [NA]
  • 23. CR-3.12 Provisioning product supplier roots of trust [NA]
  • 24. EDR-3.12, NDR-3.12 Provisioning product supplier roots of trust [Met]
  • 25. HDR-3.12/HDR-3.13 Provisioning product supplier roots of trust [NA]
  • 26. CR-3.13 Provisioning asset owner roots of trust [NA]
  • 27. EDR-3.13, NDR-3.13 Provisioning asset owner roots of trust [Met]
  • 28. CR-3.14 Integrity of the boot process[NA]
  • 29. EDR-3.14, NDR-3.14 Integrity of the boot process [Met]
  • 30. EDR-3.14 RE(1), NDR-3.14 RE(1) Authenticity of the boot process [Met]
  • References
• CIP IEC-62443-4-2 Foundational Requirement-6 & 7 Assessment details
  • 1. Overview
  • 2. CR-6.1 Audit log accessibility [Met]
  • 3. CR-6.1 RE(1) Programmatic access to audit logs [NA]
  • 4. CR-6.2 Continuous monitoring [Met]
  • 5. FR-7 Resource Availability
  • 6. CR-7.1 Denial of service protection [Met]
  • 7. CR-7.1 RE(1) Manage communication load from component [Met]
  • 8. CR-7.2 Resource Management [NA]
  • 9. CR-7.3, CR-7.03 RE(1), CR-7.4 Control system backup, integrity verification [NA]
  • 10. CR-7.5 Emergency Power [NA]
  • 11. CR-7.6 Network and security configuration settings [Met]
  • 12. CR-7.6 RE(1) Machine-readable reporting of current security settings [NA]
  • 13. CR-7.7 Least functionality [Met]
  • 14. CR-7.8 Control system component inventory [Met]
  • References
• CIP IEC-62443-4-2 Foundational Requirement-2 Assessment details
  • 1. Overview
  • 2. CR-2.1 Authorization enforcement [Met]
  • 3. CR-2.1 RE(1) Authorization enforcement for all users (humans, software processes and devices) [Met]
  • 4. CR-2.1 RE(2) Permission mapping to roles [Met]
  • 5. CR-2.2 Wireless use control [NA]
  • 6. CR-2.3 Use control for portable and mobile devices [NA]
  • 7. CR-2.4 Mobile code [NA]
  • 8. EDR 2.4, HDR 2.4, NDR 2.4, SAR 2.4 Mobile code [NA]
  • 9. EDR 2.4 RE(1), HDR 2.4 RE(1), NDR 2.4 RE(1), SAR 2.4 RE(1) Mobile code authenticity check [NA]
  • 10. CR-2.5 Session lock [NA]
  • 11. CR-2.6 Remote session termination [Met]
  • 12. CR-2.7 Concurrent session control [NA]
  • 13. CR-2.8 Auditable events [Met]
  • 14. CR-2.9 Audit storage capacity [Met]
  • 15. CR-2.9 RE(1) Warn when audit record storage capacity threshold reached [NA]
  • 16. CR-2.10 Response to audit processing failures [Met]
  • 17. CR-2.11 Timestamps [Met]
  • 18. CR-2.11 RE(1) Time synchronization [Met]
  • 19. CR-2.11 RE(2) Protection of time source integrity [NA]
  • 20. CR-2.12 Non-repudiation [Met]
  • 21. CR-2.12 RE(1) Non-repudiation for all users [NA]
  • 22. CR 2.13, EDR-2.13 RE(1), HDR-2.13 RE(1), NDR-2.13 RE(1) Activer Monitoring [NA]
  • References
• CIP IEC-62443-4-2 Foundational Requirement-4 & 5 Assessment details
  • 1. Overview
  • 2. CR-4.1 Information confidentiality [Met]
  • 3. CR-4.2 Information persistence [Met]
  • 4. CR-4.2 RE(1), CR-4.2 RE(2) Erase of shared memory resources, Erase verification [NA]
  • 5. CR-4.3 Use of cryptography [Met]
  • 6. CR 5.1, NDR-5.1 Network segmentation [NA]
  • 7. CR 5.2 Zone boundary protection [NA]
  • 8. NDR 5.2, NDR 5.2 RE(1), NDR 5.2 RE(2), NDR 5.2 RE(3) Zone boundary protection, Deny all and permit by exception, Island mode, Fail close [NA]
  • 9. CR 5.3, NDR 5.3 General-purpose person-to-person communication restrictions [NA]
  • 10. CR 5.4 Application partiontiong [NA]
  • References
• Secure Ciphers investigation
  • 1. Objective
  • 2. Technical guidelines from BSI & NIST
  • 3. Key points of the BSI guidelines
  • 4. Part-1 of BSI technical guidelines
  • 5. Part-2 of BSI technical guidelines
  • 6. How to use these guidelines (cipher suite list)
  • Key References
• CIP IEC-62443-4-2 Assessment Result
  • 1. Overview
  • 2. Reference hardware for IEC-62443-4-2 assessment
  • 3. Software Components
  • 4. Target Security Level
  • 5. Target device category
  • 6. Assessment Results
  • 7. CIP IEC-62443-4-2 Assessment Summary
• Secure Boot Authenticity Verification for CIP Image (RST)
  • 1. Install efitools & Generate Keys
  • 2. Prepare USB Stick with Keys & KeyTool
  • 3. Inject Secure Boot Keys into M-COM BIOS
  • 4. Expected Boot Failure — Verification
  • Reverting Changes — Restore Normal Boot
  • Footnotes

security

• CIP-Security-CodingGuideLines
  • Introduction
  • CIP Project coding standards
  • CIP Upstream projects coding standards
  • Tools to assist security code review
• Static analysis tools for CIP packages
  • IEC-62443 Requirement for Static Code Analysis
  • Coverity Scan
  • Gitlab SAST
  • Key points:
  • Next Step
• CIP-Security-CodingGuideLines
  • Introduction
  • CIP Project coding standards
  • CIP Upstream projects coding standards
  • Tools to assist security code review
• CIP Security Hardening
  • Introduction
  • Assumptions
  • 1. Scope
  • 2. Terms
  • 3. Hardening Guidelines
  • 4. Technical Implementation details
  • 5. Normative references
  • 6. History
• Checklist for compliance to IEC-62443-4-1
  • Purpose
  • Scope
  • Checklists
  • Supply Chain
  • Development Process
  • Vulnerability Management
  • Documentation
• [CIP-Security] [CR2.10] Response to audit processing failure
  • 1. Objective
  • 2. Common Approach for Response to audit processing failure
  • 2.1. Alert the allocated audit log storage volume is nearly full
  • 2.2. Take the actions to response to audit log processing failure
  • 3. CIP Features for Response to Audit Processing Failure
  • 3.1. auditd
  • 3.2. The log daemon not support the space left, error detection or max log file features
  • Reference
• CIP Development Environment Security
  • 1. Objective
  • 2. Assumptions
  • 3. Scope
  • 4. Security Requirement
  • 5. CIP Development Environment
  • 6. Policy for CIP repository maintainer privilege
  • 7. Current CIP repositories and maintainers
  • 8. References
• CIP Security Partitions
  • 1. Objective
  • 2. Partitions
• iec62443-4-2-FR-1
  • Tests reference and CIP recommendation
  • Default action
• iec62443-4-2-FR-2
  • Tests reference and CIP recommendation
  • Default action
• iec62443-4-2-FR-3
  • Tests reference and CIP recommendation
  • Default action
• iec62443-4-2-FR-4
  • Tests reference and CIP recommendation
  • Additional notes
• iec62443-4-2-FR-5
  • Tests reference and CIP recommendation
• iec62443-4-2-FR-6
  • Tests reference and CIP recommendation
• iec62443-4-2-FR-7
  • Tests reference and CIP recommendation
• IEC 62443-4-2 App & HW Guidelines
  • 1. Objective
  • 2. Acronyms
  • 3. Assumptions
  • 4. Scope
  • 6. CIP Security packages
  • 7. IEC Security Layer
• OWASP Top 10 Vulnerabilities Monitoring
  • 1. Objective
  • 2. OWASP Top 10 Vulnerabilities
  • 3. CIP features for system monitoring
  • 4. References
• CIP Private Key Management
  • 1. Objective
  • 2. Assumptions
  • 3. Scope
  • 4. Security Requirement
  • 5. General Private Key Management Steps
  • 6. About CIP Private Keys
  • 7. Private Key Management Best Practices
  • 8. References
• CIP Security Requirements
  • Overview
  • IEC-62443-4-2 Requirements
  • Other Security Requirements
• CIP Threat Modeling
  • 1. Objective
  • 2. Assumptions
  • 3. Scope
  • 4. Security Requirements
  • 5. Threat Modeling Strategy
  • 6. Data Flow Diagrams(DFD)
  • 7. Potential Threats To the System and Mitigation
  • 8. CIP Core Packages for mitigation
  • 9. CIP Kernel Threat Modeling
  • 10. Updating CIP Threat Model
  • 11. Further Guidelines for End Product owners
  • 12. Acronyms
  • 13. CIP Core CVE scanner
  • 14. CIP Kernel CVE scanner
  • 15. References
• User Security Manual
  • 1. Objective
  • 2. Assumptions
  • 3. Scope
  • 4. Guidelines
  • 5. CIP System Monitoring
  • 6. Generating CVE report for the installed packages

testing

• Upstream testing results of CIP IEC Layer packages
  • 1. Introduction
  • 2. Scope
  • 3. Autopkgtest results in Debian CI
  • 4. Packages with no Debian CI results but has upstream tests
  • 5. Packages with no Debian CI results nor upstream tests
• CIP Penetration Testing
  • Objective
  • Penetration testing
  • CIP Penetration Testing
  • References

user

• CIP User Manual
  • 1. Overview
  • 2. Civil Infrastructure Platform
  • Reference Hardware
  • Open Source Base Layer (OSBL)
  • How to Create CIP Images
  • Default User Accounts
  • Porting CIP for New Hardware
  • CIP Testing
  • CIP Software Updates
  • CIP System Monitoring
  • Password policies
  • References

TODO

• TODO List for further improvements of IEC documents