Skip to content

Security perspective ​

Lens: Trust boundaries — data in AI prompts, scan gates, threat models, incidents, and policy exceptions.

Phase by phase ​

PhaseYour jobKey artifactsGuides & SOPs
PlanData classification on intakeClass label on ticketData governance · SOP-001
DefineThreat model review (T1/T2 external)STRIDE outlinePlanning & ADR
BuildSAST/SCA/secrets policyScan thresholdsLinters · AI guardrails · Identity & secrets
VerifyBlock Critical; exception processSOP-012SOP-005
ReleaseDAST on staging; container CVEsScan reportCI/CD
OperateGuardDuty; breach playbooksSecurity incidentIncident mgmt
LearnPostmortem for Sev-1 securityPolicy updateSOP-008

Non-negotiables ​

RuleReference
No prod PII in AI promptsSOP-010
No merge on Critical secret scanSOP-005
Restricted data never in coding-agent RAGData governance
Security exceptions time-boundSOP-012

Who you collaborate with ​

RoleWhen
AIPOAI platform audit, Bedrock logging
Data stewardClassification glossary
ArchitectSecurity ADRs
DevOpsWAF, IAM, GuardDuty, Secrets Manager
Legal/privacyBreach and erasure

Pitfalls (Security view) ​

PitfallMitigation
Consumer AI tools for codeEnterprise tier only
Permanent scan exceptionsMax 30d + remediation
Logs with full PIIRedaction standards
AI RCA on malware in public modelsIsolated analysis

← All roles

Reference template only — no production code. Adapt in your own project.