# Deployment security assurance **This is a proposed local checklist. No deployment security assessment has been performed.** Use it to apply the [Secure by Design guidance](https://nhs-smartcard-printing-wiki.pages.dev/secure-by-design/index.md) to an actual RA service. Agree its scope and evidence with the local security, information governance and RA owners. For the organisational assessment route, read [CAF-aligned DSPT explained](https://nhs-smartcard-printing-wiki.pages.dev/caf-dspt/index.md) and [DSPT scope and evidence for RA services](https://nhs-smartcard-printing-wiki.pages.dev/dspt-assessment/index.md). They distinguish outcome evidence, assigned profiles and the annual independent audit from this deployment checklist. ## Design and evidence checklist The outcomes below translate published guidance into this wiki's hardware, software and connectivity model. The suggested records are local recommendations. They do not add NHS installation prerequisites or reproduce a complete CAF assessment. | Area | Proposed local action | Evidence to retain | Guidance | |---|---|---|---| | Ownership and scope | Identify the service owner, security decision-maker, support owner and applicable assurance route. Map the functions that depend on card issuance. | Scope statement, responsibilities and risk decisions. | [SRC-028](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-028), [SRC-029](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-029) | | Hardware and physical access | Inventory the workstation, both readers and printer. Assess access to devices, blank cards and printed output. | Device register, location/access decisions and handling procedure. | Local application of [SRC-027](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-027); device baseline [SRC-002](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-002), [SRC-003](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-003) | | Software and suppliers | Maintain an approved component list. Check package origin, support status, installation privileges, updates and rollback. Resolve prerequisite failures before acceptance. | Version inventory, package approvals and change records. | [SRC-025](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-025), [SRC-030](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-030) | | Operator and administrator access | Review who can issue cards, change the build and approve access. Test card removal and session behaviour. | CIM role review, administration model and test results. | RA roles [SRC-011](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-011); secure access [SRC-027](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-027) | | Connectivity and local interfaces | Document internet, local browser/service and USB paths. Review gateway rules and browser exceptions against the required domains. Assess any remote redirection separately. | Data-flow record, rule ownership and tested configuration. | [SRC-006](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-006), [SRC-010](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-010), [SRC-030](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-030) | | Information handling | Identify personal data in the workflow, diagnostic logs and print output. Agree access, retention and disposal; assess whether a DPIA is needed. | Information assessment and approved handling rules. | [SRC-025](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-025), [SRC-029](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-029) | | Detection and recovery | Agree useful logs, fault escalation and recovery after interruption. Test the approved rebuild or alternative issuance route. | Logging design, recovery procedure and exercise results. | [SRC-027](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-027), [SRC-030](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-030) | | Change and continued assurance | Review security and functional effects before changing a runtime, driver, browser or network rule. Repeat affected checks. | Change approval, test evidence and residual-risk decision. | [SRC-025](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-025), [SRC-032](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-032) | ## Questions for the design review Use these deployment-specific prompts to test the proposed controls. They are local analysis prompts, not a published NHS threat model. - Could an unauthorised person use the operator's active session or change the workstation configuration? - Could an unapproved package, USB device or browser exception expose a local service? - Could a driver or runtime change stop card personalisation while ordinary sign-in still works? - Could an interrupted issue or print operation leave an incomplete card or expose printed information? - Can the RA service recover if the workstation, printer or internet path fails? Record the scenario, existing control, proposed action, owner and residual risk. Keep sensitive architecture details and operational evidence in the organisation's controlled records. This public wiki contains only generic guidance. ## Approval and operation 1. Agree the scope and applicable guidance using [Secure by Design](https://nhs-smartcard-printing-wiki.pages.dev/secure-by-design/index.md#which-guidance-applies). 2. Complete the component inventory and review the [runtime](https://nhs-smartcard-printing-wiki.pages.dev/workstation/index.md#resolve-the-runtime-ambiguity) and [Series 10 interface](https://nhs-smartcard-printing-wiki.pages.dev/series-10/index.md#printer-support-and-interface) qualifications. 3. Run the relevant [acceptance tests](https://nhs-smartcard-printing-wiki.pages.dev/acceptance/index.md), including security review and the complete issue-and-print workflow. 4. Record outstanding risks, their owners and the local approval decision. 5. Maintain the evidence through changes using [support and maintenance](https://nhs-smartcard-printing-wiki.pages.dev/operations/index.md). Retain actual evidence outside this public repository. A completed checklist does not itself establish NHS endorsement, DSPT compliance or operational acceptance.