{"description":"Runs automatically on a new System item that is not a vendor (System.vendor is false). Take a new system from control requirements through a system risk review, testing and acceptance to an evidenced go-live readiness decision. The approved system risk review record sets the System item's last and next assessment dates; the yearly System & Third-Party Risk Review takes over from there. Deliver the reviewed result and open actions to the responsible register owner and the named companion procedure.","edges":[{"id":"e-sdlc-requirements-system-risk-assessment","source":"sdlc-requirements","target":"system-risk-assessment"},{"id":"e-system-risk-assessment-system-review-closure","source":"system-risk-assessment","target":"system-review-closure"},{"id":"e-system-review-closure-sdlc-closure","source":"system-review-closure","target":"sdlc-closure"}],"isPublic":true,"itemTypeSlug":"system","metadata":{"capabilities":["new-system-implementation"],"controlVerbs":{"UC-CONFIG-10":"operates","UC-RISK-18":"operates","UC-SDLC-03":"operates","UC-SDLC-07":"operates"},"controls":["UC-SDLC-03","UC-SDLC-07","UC-CONFIG-10","UC-RISK-18"],"department":"it","domains":["controls"],"kind":"new-system-implementation","library":{"aliases":[{"source":"studio-seed","sourceTemplateId":"coworkcanvas:template:new-system-implementation"}],"canonicalUrl":"https://evidenceflows.com/workflows/all/?w=controls-system-implementation-readiness","contentDigest":"sha256:dd8e6cec106759168daf095a70661a2ba0b04f014500643ee8de65c228517741","prerequisites":{"anchorItemType":{"slug":"system"},"evidenceDestinations":[{"description":"Restricted native step results, attached documents, durable item fields and native approvals.","id":"review-evidence"}],"fields":[{"itemTypeSlug":"system","key":"vendor"},{"itemTypeSlug":"system","key":"reassessment_cadence"},{"itemTypeSlug":"system","key":"last_assessment_date"},{"itemTypeSlug":"system","key":"next_reassessment_date"}],"handoffs":[{"direction":"output","name":"Reviewed register result and open actions","sourceTemplateId":"workflow-library:controls-secure-sdlc-phase-gate-program"}],"roles":[{"contribution":"expertise","description":"Business and control sponsor. Confirm requirements and control design.","id":"reviewer-1","nodeIds":["sdlc-requirements"]},{"contribution":"expertise","description":"System owner and technical specialist. Assess system and third-party risk.","id":"reviewer-3","nodeIds":["system-risk-assessment"]},{"contribution":"approval","description":"Independent system-risk reviewer. Approve system risk review record.","id":"reviewer-4","nodeIds":["system-review-closure"]},{"contribution":"approval","description":"Go-live authority. Approve implementation record.","id":"reviewer-2","nodeIds":["sdlc-closure"]}],"status":"declared"},"provenance":[{"source":"brain/scripts/studio-seed","sourceTemplateId":"coworkcanvas:template:new-system-implementation"}],"releaseId":"sha256:dd8e6cec106759168daf095a70661a2ba0b04f014500643ee8de65c228517741","schemaVersion":1,"sourceTemplateId":"workflow-library:controls-system-implementation-readiness"},"lineOfDefense":"operate","mappingStatus":"mapped","risks":[],"slug":"controls-system-implementation-readiness","source":"coworkcanvas-gallery","standards":[],"teams":["it"]},"name":"New System Implementation (SDLC)","nodes":[{"data":{"instructions":"**Objective**\nConfirm requirements and control design. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Review the System item, business and functional requirements, the process and data flows the system will serve, applicable framework requirements, the existing control set it replaces, and architecture review output.\n\n**Procedure**\n1. Derive control requirements from the processes and obligations the system will carry rather than from vendor capability, identify controls the system cannot support, and record where a compensating manual control will be required.\n\n**Record in AssureSwarm**\n1. Capture the implementation scope, control requirements traced to processes and obligations, controls the platform cannot support, planned compensating controls, architecture review outcome, and unresolved requirement gaps.\n\n**Exit criteria**\nBusiness and control sponsor provides expertise: Control requirements are derived from obligations rather than from product capability, unsupported controls are named before build, and compensating controls are planned rather than discovered at go-live.","kind":"task","label":"Confirm requirements and control design","requiredApprovals":1},"id":"sdlc-requirements"},{"data":{"controls":["UC-CONFIG-10"],"instructions":"**Objective**\nAssess system and third-party risk. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Review the System item, architecture and data-flow records, inventory, contracts, service descriptions, business impact analysis, prior assessments, incidents, changes, user populations, and provider documentation.\n2. Use the confirmed scope, risk criteria, due-diligence responses, security and privacy evidence, service performance, incidents, vulnerabilities, continuity tests, contract terms, change history, monitoring, and prior findings.\n3. Use the implementation scope, control requirements, architecture review outcome and planned compensating controls from Confirm requirements and control design.\n\n**Procedure**\n1. Reconcile inventory and ownership, map data types and trust boundaries, identify critical business processes and integrations, distinguish provider and customer responsibilities, identify material fourth parties, and document scope changes.\n2. Evaluate threats and business impacts, inspect control and performance evidence, assess concentration and exit risk, compare contract commitments to practice, analyze incidents and changes, and challenge ratings based only on questionnaires or attestations.\n\nMap data flows, access boundaries and system/provider dependencies explicitly and inspect associated security/control coverage.\n\n**Record in AssureSwarm**\n1. Capture the review period, system and service scope, owners, provider, environments, data classification, users, integrations, critical processes, subservices, locations, changes, exclusions, and information gaps.\n2. Document risk ratings and direction, criteria, evidence, control strengths and gaps, provider and customer responsibilities, concentration and resilience concerns, incidents, uncertainties, and prior-period comparison. Also record risk assessment.\n\n**Exit criteria**\nSystem owner and technical specialist provides expertise: The review boundary and responsibility model are unambiguous, critical dependencies are represented, and missing information that could affect risk is assigned. The assessment is reproducible, material gaps and uncertainty remain visible, and rating changes or reliance on provider evidence are supported before response selection.","kind":"task","label":"Assess system and third-party risk","requiredApprovals":1},"id":"system-risk-assessment"},{"data":{"controls":["UC-RISK-18"],"instructions":"**Objective**\nApprove system risk review record. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Use the completed assessment, open findings, service roadmap, remediation commitments, contract rights, business continuity and exit plans, stakeholder needs, appetite criteria, and proposed monitoring indicators.\n2. Review every stage result, source evidence, ratings, provider and customer responsibilities, response approval, linked issues, monitoring commitments, contract actions, and information gaps.\n\n**Procedure**\n1. Compare continued use, remediation, restriction, replacement, and exception paths; define commitments and evidence; confirm decision authority; set performance and risk triggers; plan escalation and exit readiness; and create linked actions.\n2. Trace material ratings and decisions to evidence, verify commitments and dates, reconcile inventory and linked records, confirm contrary evidence remains visible, and return unsupported or inconsistent analysis for correction.\n\n**Record in AssureSwarm**\n1. Record the decision, rationale, authorized approver, remediation commitments, monitoring indicators and cadence, contract actions, restrictions, contingency or exit steps, linked issues, owners, and due dates. Also record response decision; monitoring plan.\n2. Capture the authorized reviewer, review summary, accepted ratings and response, review effective date, monitoring cadence, provider commitments, linked issues, limitations, owners, and due dates. Also record system risk review summary.\n3. After this step is approved, update the System item: set `System.last_assessment_date` to the approval date and `System.next_reassessment_date` to that date plus `System.reassessment_cadence` (quarterly adds 3 months, semi_annual 6, annual 12, biennial 24; for ad_hoc, leave the next date for the risk owner to set).\n\n**Exit criteria**\nIndependent system-risk reviewer provides approval: An approver accepts that the response follows from risk and criticality, decision authority is confirmed, and monitoring and action commitments are measurable. The authorized reviewer accepts the review as a traceable record of work and decisions, related records can be updated consistently, and closure is not represented as assurance. After approval, the System item's `last_assessment_date` equals the approval date and `next_reassessment_date` follows its `reassessment_cadence`.","kind":"task","label":"Approve system risk review record","requiredApprovals":1},"id":"system-review-closure"},{"data":{"controls":["UC-SDLC-03","UC-SDLC-07"],"instructions":"**Objective**\nApprove implementation record. The reviewer decides from the complete package described below.\n\n**Inputs**\n1. Use test strategy and phase plans, executed unit, integration, and user acceptance results, defect logs with severity and status, the UAT tester identities, and the acceptance criteria agreed at requirements.\n2. Use acceptance results and open defects, control requirement coverage, cutover and rollback plans, data conversion readiness, support and monitoring arrangements, and the agreed go-live criteria.\n3. Review all stage records, requirement traceability, executed test evidence, UAT independence, defect dispositions, readiness criteria assessment, and open conditions with owners.\n4. Use the approved system risk review record from Approve system risk review record: accepted ratings, the response decision, conditions and the monitoring plan. Do not approve go-live while a condition from that record is open without an owner and date.\n\n**Procedure**\n1. Inspect executed results per phase, confirm UAT testers are business users by identity rather than by role label, trace open defects to a severity-based acceptance decision, and test the control requirements specifically rather than only functionality.\n2. Test the decision against the criteria agreed at requirements rather than against schedule pressure, confirm rollback is demonstrated rather than documented, verify compensating controls are operating, and record conditions with owners and deadlines.\n3. Trace every control requirement to a test result or a named compensating control, verify conditions carry deadlines, confirm the go decision cites criteria rather than schedule, and return untested control requirements with precise comments.\n\n**Record in AssureSwarm**\n1. Document test phases with executed results and dates, control requirements tested and their outcomes, defects by severity with status, UAT tester identities and independence, acceptance status, and untested requirements.\n2. Record the readiness decision against each criterion, residual risks and their owners, cutover and rollback evidence, compensating controls confirmed operating, conditions with deadlines, and criteria not met.\n3. Capture the authorized reviewer, the summary, accepted readiness decision, go-live date, residual risks and conditions with owners and dates, compensating controls in force, and linked issues raised. Also record implementation summary.\n\n**Exit criteria**\nGo-live authority provides approval: Each phase is evidenced by executed results, UAT independence is demonstrated by identity, control requirements are tested distinctly from functionality, and open defects carry a severity-based decision. An approver accepts that readiness is measured against the pre-agreed criteria, rollback capability is demonstrated, and unmet criteria are carried as conditions with owners rather than waived silently. The authorized reviewer accepts the record as evidence the implementation control operated, and closure implies no assurance over control requirements deferred to post-go-live.","kind":"task","label":"Approve implementation record","requiredApprovals":1},"id":"sdlc-closure"}],"sourceTemplateId":"workflow-library:controls-system-implementation-readiness"}
