Security & Compliance Workflows
Ensure security and compliance requirements are met before production deployments with mandatory review checklists.
Security Review Checklist (Mandatory Before Production)
Mandatory security review that must be completed before any production deployment. This checklist cannot be bypassed.
Workflow Structure:
- Security Review Section:
- SAST scan passed ✓
- Secrets check completed ✓
- Third-party licenses approved ✓
- Pen-test complete ✓
- Vulnerability assessment done ✓
- Security architecture reviewed ✓
- Data encryption verified ✓
- Attach File Items - Required security documentation
- SAST scan reports
- Pen-test results
- Security review sign-off
- Threat model documentation
- Blocker Trigger - Stops final "Deploy to Prod" section until all security items are complete
- Notify Trigger - Alerts #security team automatically when review starts and when it passes
- Change Assignee Trigger - Auto-assigns to security team for review
🔒 Security Gate: This blocker cannot be bypassed, ensuring no code reaches production without proper security review.
GDPR / SOC2 / ISO Audit Trails
Maintain comprehensive audit trails for compliance requirements with mandatory evidence collection.
Workflow Structure:
- Compliance-Related Tasks as Nested Checklist
- Data processing impact assessment
- Privacy policy updates
- User consent mechanisms verified
- Data retention policies reviewed
- Access controls validated
- Encryption standards verified
- Attach File Items - Force evidence upload
- Signed compliance documents
- Audit reports
- Policy acknowledgments
- Training completion certificates
- Convert Failed Items - Turn compliance failures into audit findings as separate issues
- Blocker Triggers - Ensure proper sequencing of compliance tasks
- Notify Triggers - Alert compliance team of status changes
Security Incident Response Workflow
Structured response process for security incidents with clear escalation paths and documentation requirements.
Workflow Structure:
- Initial Response
- Incident identified and logged
- Severity assessed
- On-call security team notified
- Blocker → Investigation
- Root cause analysis
- Impact assessment
- Evidence collection
- Blocker → Containment
- Threat isolated
- Affected systems secured
- Backup systems verified
- Blocker → Remediation
- Vulnerability patched
- Systems restored
- Monitoring enhanced
- Post-Incident Review
- Lessons learned documented
- Process improvements identified
- Compliance reporting completed
Third-Party Security Review
Comprehensive review process for third-party integrations and dependencies.
Review Checklist:
- Vendor security assessment completed
- Data processing agreement signed
- Security questionnaire answered
- Penetration test results reviewed
- Compliance certifications verified
- Data residency requirements met
- Incident response procedures documented
Blocker: Third-party integration cannot be deployed until all security review items are complete.
Best Practices
- Never bypass security review blockers - they exist to protect your organization
- Always require file attachments for security documentation to maintain audit trails
- Use notify triggers to ensure security team is immediately aware of review requests
- Convert security findings into separate issues for proper tracking and resolution
- Structure compliance checklists to match your certification requirements (GDPR, SOC2, ISO)
- Use blockers between security review phases to ensure proper sequencing
- Leverage change assignee triggers to route security reviews to appropriate team members