Configurable role profile
Engineer security into every delivery decision.
Yellow Team pathways develop secure-by-design engineering: threat modelling before code exists, secure coding and review, automated security testing in the pipeline, software bill of materials and provenance verification, and remediation that prevents recurrence. Laboratories provide isolated repositories, build pipelines and registries so learners practise the full delivery loop. Assessment weighs remediation quality and whether a defect class returns, not the count of findings discovered.
CLIP · Yellow Team role profile
Illustrative view- 01 · Mission outcomeDesign, build and verify software using secure-by-design and DevSecOps practices.
- 02 · CompetenciesThreat modelling · Secure coding · Code review · Security testing
- 03 · Exercise activitySecure API sprint
- 04 · EvidenceThreat model with identified misuse cases
Team-colour terminology varies by organization
Mission intent
The role's purpose and its boundaries.
Design, build and verify software using secure-by-design and DevSecOps practices.
Core competencies
What this pathway develops.
Competencies are versioned and mapped to organizational, NICE, relevant SKKNI or custom frameworks without duplicating the underlying evidence.
- 01Threat modelling
- 02Secure coding
- 03Code review
- 04Security testing
- 05Software bill of materials
- 06Remediation
Learning pathway
Progressive difficulty, evidence at every step.
- 01FoundationStructured learning and prerequisites.
- 02Guided labSupervised practice with checkpoints.
- 03Team labCoordination and handoffs within the role.
- 04Integrated exerciseMulti-team scenario under exercise control.
- 05AssessmentObserved performance and assessor adjudication.
In sequence: Foundation knowledge leads into a guided laboratory, then a team laboratory, then an integrated multi-team exercise, and finally an assessment that produces competency evidence.
Representative scenarios
How the pathway is exercised.
Secure API sprint
Designing, building and verifying an interface against misuse cases.
Pipeline policy failure
Diagnosing and correcting a build that fails a security policy gate.
Malicious dependency response
Detecting, containing and remediating a compromised component.
Tools and environments
Capability categories, not a tool list.
Specific tooling is selected per deployment after security, licence and air-gap review. The categories below describe what the pathway needs to work.
- Isolated repositories, pipelines and artifact registries
- Static, dynamic, composition, secret and container analysis tooling
- Vulnerable-by-design applications under promotion controls
Evidence of competence
What observable behaviour supports readiness.
A readiness claim for this role must trace back to these artifacts. Evidence freshness is tracked separately from current competence, so an expired record never silently counts as a current one.
How readiness is calculated- Threat model with identified misuse cases
- Code change and review record
- Scan results by control, not only severity
- Software bill of materials and signed artifact
- Recurrence test proving the class is closed
Collaboration
Upstream and downstream handoffs.
No role operates alone. These are the relationships that make this pathway useful to the wider mission.
Receives exploit context from Red Team through Orange Team translation
Supplies fixes and tests that Blue Team can verify operationally
Shares supply-chain findings with platform operations
Metrics
Operational and learning measures.
What the platform can measure for this role. Targets are baselined with each organization rather than claimed in advance.
- Remediation quality
- Vulnerability recurrence
- Pipeline policy compliance
- Escaped defects and provenance completeness
Map your roles to CLIP.
We will work from your approved role definitions and competency framework, not from ours.