C5 (Germany)
C5: Asset Management

C5 (Germany) C5-AM-03: Commissioning of Hardware

Approve hardware before it enters the production environment through a process that identifies, analyses and mitigates the risks its introduction creates, granting approval only after verifying that error handling, logging, encryption, authentication and authorisation are securely configured for the intended use.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 50 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-161 Rev 1 · 7 controls

FedRAMP High · 6 controls

  • CA-9 Internal System Connections
  • CM-2 Baseline Configuration
  • CM-3 Configuration Change Control
  • CM-8(1) Updates During Installation and Removal
  • MA-2 Controlled Maintenance
  • PE-16 Delivery and Removal

FedRAMP Moderate · 6 controls

  • CA-9 Internal System Connections
  • CM-2 Baseline Configuration
  • CM-3 Configuration Change Control
  • CM-8(1) Updates During Installation and Removal
  • MA-2 Controlled Maintenance
  • PE-16 Delivery and Removal

NIST SP 800-53 Rev 5 · 4 controls

CMMC 2.0 · 3 controls

ISO 27001:2022 · 3 controls

  • 5.9 Inventory of information and other associated assets
  • 7.13 Equipment maintenance
  • 8.9 Configuration management
  • AM-2 Use only approved services
  • AM-3 Ensure security of asset lifecycle management

CIS Controls v8 · 2 controls

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

ISO 27002:2022 · 2 controls

  • 7.13 Equipment maintenance
  • 8.32 Change management
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

NIST SP 800-172 · 2 controls

  • 3.14.7e Verify Correctness of Security Functions
  • 3.5.3e Prohibit Connection of Unknown or Unverified System Components

UK Cyber Essentials · 2 controls

  • CE-FW.2 Change Default Firewall Passwords
  • CE-SC.2 Change Default Passwords on Devices and Software
  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services

HIPAA Security Rule · 1 control

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

PCI DSS 4.0 · 1 control

  • 2.2.1 2.2.1 System configuration standards maintained

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in C5: Asset Management

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-AM-03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 50 it maps to, and the evidence behind each claim, over MCP and REST.