ETSI EN 303 645
5.4 Secure storage of sensitive security parameters – ETSI EN 303 645

ETSI EN 303 645 Provision 5.4-3: No hard-coded critical security parameters in source code

Critical security parameters such as usernames and passwords, API keys or private keys are not hard-coded in the device software source code, since reverse engineering finds them readily and obfuscation is easily broken. Status in Table B.1: M (mandatory, a shall provision).

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

What else in your programme already covers this

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

ISO 27002:2022 · 1 control

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 5.4 Secure storage of sensitive security parameters – ETSI EN 303 645

Query this from an agent

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