CSINT n8n Workflow Change Receipt
Support workflow staging release review
A human-readable evidence record for one workflow change. This is not a security certificate.
approvedThe candidate meets the current static policy and its bound staging contract passed without an external action.
Review subject
- Review ID
- wcr-0256a2bbf7ea-157461ca
- Generated
- 2026-08-04T11:10:24.706Z
- Baseline
- CSINT - Security Regression Baseline (action-free)
157461caf339f164 - Candidate
- CSINT - Security Regression Staging Target
0256a2bbf7eaa560
- Reviewer
- CSINT Research / sample evidence review
Measured release view
Workflow nodes
Baseline12
Candidate12
Connection delta: +0 / -0
Review disposition
Blocker 0To review 0Improvements 3Context 0
Open findings
Critical0
High0
Medium0
Low1
Candidate access surface
- AI agents
- 0
- Tool nodes
- 0
- External domains
- 0
- Credential types
- 0
What changed
CR-001improvement
A control boundary was strengthened: Read Safe State
The candidate introduces explicit control logic at this step. The staging receipt records whether the expected behaviour held.
CR-002improvement
A control boundary was strengthened: Validate and Queue
The candidate introduces explicit control logic at this step. The staging receipt records whether the expected behaviour held.
CR-003improvement
A control boundary was strengthened: Validate Simulated Approval
The candidate introduces explicit control logic at this step. The staging receipt records whether the expected behaviour held.
Staging evidence
passed8/8 scenarios passed; 0 external actions executed.
Open findings
- LOW AA-010
No workflow-level failure route was detected
Add a failure route that records the error, alerts the operator and prevents partial actions from being treated as success.
Evidence boundaries
- This receipt compares exported JSON and a supplied staging record. It does not inspect production credential scope or external service authorization.
- Runtime evidence is accepted only when its canonical workflow fingerprint matches the candidate in this receipt.
- Local runtime receipts are reproducible evidence records, not cryptographically signed third-party attestations.
- A passing receipt records evidence for the tested policy and contract. It is not a penetration test, compliance certificate or security guarantee.
- Node names, node types, public domains and credential types can appear in the receipt. Prompt text, parameter values and credential values are omitted.