Key-loading hardware and the passwords or authentication codes that enable it are kept in a secure setting with dual control applied, and are managed so that no individual can enable the loading of clear-text keys or components alone; the individual authentication mechanisms themselves need not be under dual control, and for loading POIs the secure setting is the one defined in Annex B.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.