Goal templates — Security Engineering — P4

Security · Security Engineering · P4 — Senior Professional

These are canon-derived frames, not advice: every line is either verbatim JobFrame canon text or a fixed template wrapping it. ⟨target⟩ / ⟨baseline⟩ / ⟨date⟩ are placeholders for the manager to fill in. Nothing here is generated by AI — rows are omitted, never invented, when the canon lacks the underlying field.

SMART goals

One row per canon core output / responsibility this level owns.

JFM responsibility (P4)

Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact

Specific: Deliver: "Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
Relevant: Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery

Specific: Deliver: "Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
Relevant: Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams

Specific: Deliver: "Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
Relevant: Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies

Specific: Deliver: "Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
Relevant: Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile

Specific: Deliver: "Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
Relevant: Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
   Relevant:    Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

2. Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
   Relevant:    Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

3. Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
   Relevant:    Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

4. Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
   Relevant:    Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

5. Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables to design architectures, lead investigations, and select methods and tooling."
   Relevant:    Advances the Security · Security Engineering mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

OKRs

Objectives from this level's core outputs; key results only where a real dimension or capability backs them.

JFM responsibility (P4)

Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"
Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"
Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"
Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"
Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"
Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"
  KR2. Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

Objective 2: Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"
  KR2. Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

Objective 3: Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"
  KR2. Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

Objective 4: Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"
  KR2. Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

Objective 5: Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"
  KR2. Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨target⟩ by ⟨date⟩

MBO areas

Key result areas from this level's responsibilities, each with a standard grounded in the canon leveling rubric where one exists.

Area	Standard	Target	Due
Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact	Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."	⟨target⟩	⟨date⟩
Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery	Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."	⟨target⟩	⟨date⟩
Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams	Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."	⟨target⟩	⟨date⟩
Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies	Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."	⟨target⟩	⟨date⟩
Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile	Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth expertise in security architecture, cloud security, and forensic investigation to complex issues with functional impact."
   Target:   ⟨target⟩   Due: ⟨date⟩

Scorecard

Only perspectives with real canon backing are shown — no Financial or Customer perspective, since nothing in the canon grounds business-financial or customer measures for a role alone.

Internal process

"Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"→ ⟨target⟩ by ⟨date⟩
"Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"→ ⟨target⟩ by ⟨date⟩
"Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"→ ⟨target⟩ by ⟨date⟩
"Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"→ ⟨target⟩ by ⟨date⟩
"Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"→ ⟨target⟩ by ⟨date⟩

Role calibration

Meets the scope bar: "A system or set of related features"→ ⟨target⟩ by ⟨date⟩
Meets the autonomy bar: "Self-directed; reviewed at critical decision points"→ ⟨target⟩ by ⟨date⟩
Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"→ ⟨target⟩ by ⟨date⟩
Meets the impact bar: "Multi-team / function outcomes"→ ⟨target⟩ by ⟨date⟩
Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"→ ⟨target⟩ by ⟨date⟩
Meets the leadership bar: "Technical lead for focused efforts; mentors several"→ ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Internal process
  - "Designs security architectures and controls for complex infrastructure and cloud environments (AWS Security Hub, Azure Sentinel, Google SCC), selecting methods and tooling with functional impact"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Leads incident investigations end-to-end, performing in-depth forensic analysis across complex variables and directing containment and recovery"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Performs deep cloud security architecture work — IAM at scale, cloud-native detection, and Terraform / Open Policy Agent guardrails — and may lead project teams"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Shifts the team from reactive monitoring toward proactive threat hunting, building reusable detection content and hunt methodologies"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Mentors junior and mid-level engineers, acting as technical decision-maker with tooling autonomy and a defined on-call profile"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]

Role calibration
  - Meets the scope bar: "A system or set of related features"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Self-directed; reviewed at critical decision points"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Multi-team / function outcomes"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Technical lead for focused efforts; mentors several"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]