Identity and trusted devices
Review authentication methods, password protection, multi-factor requirements and device trust against deployment evidence.
Security & Operational Trust
Security and accountability for technical review.
A technical briefing should establish the authentication, access boundaries, credential protection and audit evidence required by the proposed deployment.
Operational trust boundary Illustrative model
Controlled boundaryAUTHORISE
Operational controls
Identity, authority and evidence across every workflow.
Role and scope checks
Define and verify role and scope boundaries for site, installer, portfolio and market operations.
Protected market access
Establish how external participant and market credentials would be stored, rotated and protected.
Configuration and command records
Request evidence of auditing, configuration history and command records for the proposed workflow.
Deployment options
Security requirements decide where responsibilities sit.
Cloud, hybrid and site-resident responsibilities should be selected against the programme’s control, connectivity, recovery and residency constraints, not as a generic infrastructure preference.
- 01
- Define the information and command boundaries
- 02
- Assign authority and recovery ownership
- 03
- Identify the evidence required for approval