7 - Infrastructure management
The PKI implementation is a combination of software, hardware, network service, and resources that are needed to operate and manage the environment. The environment can be hosted on-premise, in the cloud, or in a hybrid environment.
Independent of the hosting model, the PKI environment needs to be properly managed and maintained, which requires resources and processes. The infrastructure management refers to management of the technical and operational components of the PKI environment, which includes software, hardware, network, equipment, facilities, and other related resources.
The PKI components may be distributed across multiple locations and managed by different teams. Therefore, it is important to have a clear description of the operational infrastructure with all dependencies and prerequisites. The infrastructure management should be aligned with the overall strategy of the organization and the scope of the PKI.
When the infrastructure and environment where the PKI is implemented are not effectively managed and maintained, the complexity of the environment increases and the risk of failure increases as well. The infrastructure is often one of the key targets for attackers, therefore it is important to ensure that it is properly secured and available.
Category maturity levels description
| Maturity level | Description |
|---|---|
| 1 - Initial | Flat network with no segmentation. No separation of environments. No network vulnerability management. No infrastructure recovery objectives. No periodic review of infrastructure activities. |
| 2 - Basic | Network and deployment infrastructure is documented and known by the infrastructure team. |
| 3 - Advanced | Infrastructure is documented and managed. Network vulnerability management is implemented. Responsibility for infrastructure is defined and approved by the management. |
| 4 - Managed | The infrastructure is properly design, documented, and maintained, including procedures for vulnerability management, recovery and continuity. |
| 5 - Optimized | Processes and procedures are formally followed and periodically reviewed. The infrastructure is properly designed, documented, and maintained by responsible personnel and integrated into the overall organizational strategy. |
Requirements
| # | Requirement | Weight |
|---|---|---|
| 1 | Network and deployment infrastructure is documented | 4 |
| 2 | Separation and segmentation principles are applied | 3 |
| 3 | Network vulnerability management is implemented and maintained | 3 |
| 4 | Infrastructure recovery objectives controls | 1 |
| 5 | Infrastructure activities are periodically reviewed | 2 |
Details
Network and deployment infrastructure is documented
Guidance
The network and deployment documentation of the infrastructure should be aligned with the architecture and design of the PKI. In other terms, it provides details about how the implementation is done in the real environment.
The network and deployment infrastructure should be properly documented and maintained. The documentation should include the following:
- PKI components and their dependencies
- Facilities and equipment
- Deployment infrastructure description
- Clustering and load balancing
- Network topology and diagram
- Communication and open ports requirements
- Supporting cloud providers and services
- Supporting systems and services (identity management, access control, logging, monitoring, etc.)
Assessment
The following is sample evidence that can be used to assess the requirement:
- Network topology and diagram
- Deployment documentation
- Sample configuration of network to compare with the documentation
- Integration with supporting and other systems
- Interview with the network administrators
References
- ISO/IEC 20000 and related standards
- ISO/IEC 27001 - Information security management systems
- Guidance for Containers and Container Orchestration Tools
Separation and segmentation principles are applied
Guidance
The PKI environment should be properly separated and segmented from other environments and systems. The separation and segmentation should be applied on all levels, including network, infrastructure, and application. The separation and segmentation should be applied based on the security requirements and risk assessment.
Segmentation isolates the PKI environment from the remaining environment and reduces the risk of unauthorized access and data leakage. It also helps to reduce the impact of a potential compromise of the PKI environment from other systems and environments. Segmentation can be achieved using a number of physical or logical methods, such as:
- Properly configured internal network security controls
- Routers with strong access control lists
- Other technologies that restrict access to a particular segment of a network
For the proper maintenance of the infrastructure and deployed PKI components, the staging/testing environment should be available in the same configuration as the production environment. If needed, development environments can be used for testing and development purposes. Production, staging, and development environments should be logically separated and isolated from each other, including the data that is used in the environments.
Assessment
The following is sample evidence that can be used to assess the requirement:
- Network topology and diagram
- Implementation of network isolation
- Separation of production and testing environments
- Sample data
- Interview with the network administrators
References
Network vulnerability management is implemented and maintained
Guidance
The network vulnerability management is a process that is used to identify, classify, remediate, and mitigate vulnerabilities in the network infrastructure and protects PKI implementation from potential attacks. The process should be implemented and maintained in order to ensure that the network infrastructure is properly secured and protected from potential attacks.
The network vulnerability management should include the following:
- Included in the overall vulnerability management process
- Periodical scanning of the network infrastructure
- Identification of vulnerabilities
- Categorization and prioritization of vulnerabilities and remediation
- Updating and patching requirements
Assessment
The following is sample evidence that can be used to assess the requirement:
- Network vulnerability management process
- Results from last network vulnerability scan
- Remediation plan
- Interview with the network administrators
References
- Common Vulnerability Scoring System (CVSS)
- ISO/IEC 20000 and related standards
- ISO/IEC 27001 - Information security management systems
Infrastructure recovery objectives controls
Guidance
In case of issues with the infrastructure, it should be possible to quickly identify the root cause and recover the infrastructure to the operational state. The recovery objectives should be defined and aligned with the overall business continuity and disaster recovery strategy of the organization.
The infrastructure should be frequently backed up and the backups should be stored in a secure location. The backups should be tested and validated on a regular basis. Infrastructure managed as code may help to reduce complexity and increase the speed of recovery.
Assessment
The following is sample evidence that can be used to assess the requirement:
- Infrastructure recovery objectives
- Backup and recovery plan
- Infrastructure configuration as a code
- Interview with the infrastructure administrators
References
Infrastructure activities are periodically reviewed
Guidance
Infrastructure management related activities should be periodically reviewed, updated and approved. The frequency of review should be based on the organizational risks and needs to be protected against current and future trends.
Periodical review helps to keep the infrastructure management accurate and helps to maintain required skills and knowledge. It provides assurance that the expected controls are active and working as intended.
The review can include the following:
- Changes made to the infrastructure
- Regular checks of firewall rules
- Review of the network topology
- Review of the network segmentation
- Regular checks of access control lists
- Vulnerability reports and timely remediation
- Review and correlation of logs
- And other activities related to the infrastructure management
Assessment
The following is sample evidence that can be used to assess the requirement:
- Infrastructure management activities review frequency
- Organizational implementation of review process
- Validation of documentation, reports, records, and reviews
