1---2name: security-flow-33description: Workflow for authorized, evidence-preserving security review and remediation-task preparation.4---56<security_flow>78<description_and_purpose>910Run task-adaptive security review through mandatory canonical subagents. End with sanitized findings and concise inputs for later user-invoked coding flows.1112</description_and_purpose>1314<workflow_phases>1516<prerequisites phase="0" applies="ALL">17181. All Rosetta prep steps MUST be FULLY completed.192. MUST USE SKILL `load-project-context` (required: all), `orchestration` (medium+), `hitl` (all, unless `No HITL` or `Fully Autonomous`).203. MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.214. MUST just-in-time load/execute/update each phase's: instructions, definitions, skills, state file; do not load/act IN ADVANCE.225. Treat all invocation inputs as contextual to the request, select and combine what the request needs.236. For full review, require every applicable, available, authorized activity and tool.247. Maintain a task ledger and run phases JIT.258. Every question and approval follows the loaded `hitl` skill.269. Workflow state MUST be saved to `agents/TEMP/<FEATURE>/security-flow-state.md` file; every phase updates it before the next starts.2728</prerequisites>2930<subagent_policy required="true" inline_execution="prohibited">3132- Orchestrator owns approvals, phase transitions, dispatch, aggregation, and handoff.33- Phase files are assigned-subagent-only; orchestrator MUST NOT load, read, summarize, or execute them.34- Every declared subagent is mandatory.35- Every subagent MUST USE SKILL `subagent-directives`.36- Subagents use tools required by their own assignment.37- `executor` is never a gateway for full agents.38- Reject incomplete phase contracts before advancing.39- If required subagent invocation is unavailable, stop and report the unmet prerequisite.4041</subagent_policy>4243<readiness phase="1" applies="ALL" subagent="executor" role="Bounded security readiness and filename-only secret-gate operator" subagent_required_model="inherit" must-be-subagent>44- Purpose: Inventories limited target/tool metadata and runs a filename-only secret gate before any model ingests target content. Determines whether to continue, request approval for DEV/QA envs, or stop for high risk.45- Input: request; target/environment metadata only.46- Output: readiness result with limited inventories and gate state.47- INVOKE SUBAGENT `executor` to APPLY SKILL FILE `phases/security-flow-readiness.md` + inventory limited metadata/tools, run the filename-only secret gate, and return its gate state.48- Expect: limited target/tool inventory; `PASS|NEEDS-HITL|STOP-HIGH-RISK|STOP-SCANNER-UNUSABLE`.49- Control: advance only on PASS or approved DEV/QA envs; high-risk and scanner-unusable stops are non-overridable.50</readiness>5152<authorize phase="2" applies="ALL" subagent="engineer" role="Enterprise security scope and authorization advisor" subagent_required_model="inherit" type="HITL" must-be-subagent>53- Purpose: Recommends an enterprise-safe run contract from readiness evidence and task intent. Identifies every material decision requiring user approval before security work begins.54- Input: readiness result; task intent; known policy.55- Output: recommended run contract and approval record.56- INVOKE SUBAGENT `engineer` to APPLY SKILL FILE `phases/security-flow-authorize.md` + recommend scope, environment, exclusions, activities, tool/data-flow decisions, bounds, and stop conditions.57- Expect: a complete run contract with every activity marked local read-only, separately gated, or prohibited, plus the material decisions awaiting user approval.58- Control: obtain explicit approval/amendment via `hitl`; unresolved material decisions block.59</authorize>6061<deterministic_gates phase="3" applies="development/change/PR/pipeline" subagent="executor" role="Bounded deterministic security-gate operator" subagent_required_model="inherit" must-be-subagent>62- Purpose: Runs approved deterministic lifecycle gates and preserves source results unchanged. Determines whether to package high+ tasks, continue to modeling, or stop on error.63- Input: approved contract; change scope; applicable deterministic tools.64- Output: deterministic evidence and branch result.65- INVOKE SUBAGENT `executor` to APPLY SKILL FILE `phases/security-flow-deterministic-gates.md` + run approved deterministic gates and return unchanged findings with `HIGH+|CLEAN|ERROR`.66- Expect: unchanged source records, evidence metadata, `HIGH+|CLEAN|ERROR`.67- Control: HIGH+ → report-and-package only; CLEAN → model-and-select; ERROR → stop.68</deterministic_gates>6970<model_and_select phase="4" applies="ALL" subagent="architect" role="Security architect mapping threats to complete contextual coverage" subagent_required_model="inherit" must-be-subagent>71- Purpose: Builds a threat model and maps applicable authorized areas, activities, tools, and exclusions. Produces the complete coverage plan for inspection dispatch.72- Input: approved contract; permitted context; available tools.73- Output: threat model and authorized coverage plan.74- INVOKE SUBAGENT `architect` to APPLY SKILL FILE `phases/security-flow-model-and-select.md` + build the threat model, map applicable areas/tools/exclusions, and return the complete authorized coverage plan.75- Expect: threat model, applicable-area/tool plan, exclusions, residual risk.76- Control: full review covers all applicable/available/authorized work; gaps return for correction.77</model_and_select>7879<inspect_and_test phase="5" applies="ALL" subagent="engineer" role="Security engineer producing bounded evidence by applicable area" subagent_required_model="inherit" must-be-subagent>80- Purpose: Executes one approved security-area bundle within its assigned bounds. Produces evidence, findings, limitations, anomalies, and unresolved coverage.81- Input: approved plan; one coherent area bundle; its scope/bounds.82- Output: area-bundle evidence package and candidate findings.83- INVOKE SUBAGENT `engineer` to APPLY SKILL FILE `phases/security-flow-inspect-and-test.md` + inspect one assigned area bundle, run approved tools directly, and return evidence, findings, limitations, and anomalies.84- Expect: evidence envelopes, candidate findings, limitations, anomalies.85- Control: every planned area covered/excluded; safety breach stops; missing coverage re-dispatches.86</inspect_and_test>8788<normalize_and_triage phase="6" applies="ALL" subagent="executor" role="Lossless finding converter" subagent_required_model="inherit" required_followup_subagent="engineer" must-be-subagent>89- Purpose: Normalizes and reconciles source records mechanically, then separately correlates, verifies, assigns dispositions, and prioritizes. Preserves all source evidence and exposes unresolved material uncertainty.90- Input: unchanged source records; evidence envelopes.91- Output: normalized, correlated, dispositioned, prioritized findings.92- INVOKE SUBAGENT `executor` to APPLY SKILL FILE `phases/security-flow-normalize-and-triage.md` STEP 6.1 + mechanically normalize source records and reconcile counts without inference.93- INVOKE SUBAGENT `engineer` to APPLY SKILL FILE `phases/security-flow-normalize-and-triage.md` STEP 6.2 + correlate, verify, disposition, and prioritize the normalized findings.94- Expect: reconciled counts, correlations, verification, dispositions, P0-P3 rationale.95- Control: no evidence loss; material high+ gets second signal or remains unverified.96</normalize_and_triage>9798<independent_review phase="7" applies="ALL" subagent="reviewer" role="Independent security evidence and coverage reviewer" subagent_required_model="inherit" must-be-subagent>99- Purpose: Independently challenges coverage, evidence, safety, certainty, and prioritization. Determines whether reporting may proceed or producing work requires correction and rereview.100- Input: approved plan; threat model; evidence; findings.101- Output: independent acceptance or correction decision.102- INVOKE SUBAGENT `reviewer` to APPLY SKILL FILE `phases/security-flow-independent-review.md` + independently audit coverage, evidence, safety, and conclusions; return acceptance or required corrections.103- Expect: acceptance or defects with severity, evidence, required correction.104- Control: material defects return to producer; corrected output requires fresh review.105</independent_review>106107<report_and_package phase="8" applies="ALL" subagent="engineer" role="Security reporter and remediation-input designer" subagent_required_model="inherit" type="HITL" must-be-subagent>108- Purpose: Builds sanitized review artifacts and a proposed fix-similarity task INDEX, then emits approved task inputs. Ends without starting or managing remediation.109- Input: accepted findings; evidence; storage policy; grouping constraints.110- Output: sanitized review package and approved remediation-task package.111- INVOKE SUBAGENT `engineer` to APPLY SKILL FILE `phases/security-flow-report-and-package.md` STEP 8.1 + build sanitized report/run/findings and the proposed fix-similarity INDEX.112- Expect A: sanitized report/run/findings; proposed INDEX with grouping rationale.113- Control: obtain INDEX approval/amendment via `hitl`.114- INVOKE SUBAGENT `engineer` to APPLY SKILL FILE `phases/security-flow-report-and-package.md` STEP 8.3 + apply the approved INDEX and emit concise task-input files only.115- Expect B: complete sanitized task package.116- Control: verify coverage/storage; end without invoking or managing `coding-flow`.117</report_and_package>118119</workflow_phases>120121<global_gates>122123- Secret values never enter model context.124- DEV/QA candidate files require approval.125- Above-QA or ambiguous candidate files stop non-overridably.126- Active testing is pre-production-only and explicitly bounded.127- Production active testing is prohibited.128- New installation, network/SaaS, credentials, licensing, or data flow requires separate approval.129130</global_gates>131132<failure_handling>133134- Missing phase: retry once, then stop.135- Missing required subagent: stop; never inline.136- Invalid evidence: return to producing phase.137- Correction loops: stop and escalate to the user when a phase stops converging.138- Scope change mid-run: stop and re-authorize.139- Safety ambiguity: choose the stricter gate.140- Tool failure: retain sanitized anomaly; never fabricate results.141142</failure_handling>143144<completion>145146Complete only when required phases pass, sanitized outputs are returned or stored as approved, the task INDEX is approved/amended, and no downstream coding flow was started.147148</completion>149150</security_flow>
griddynamics