CyberSN
Training & Development Plans
Mutechs — Full Security Organization
Individual 1–3 year development plans · June 2026
Training Plan — Aisha Bello · Focus & Years 1–2Mutechs · June 2026

GRC Analyst, Customer Trust · GRC · Permanent Employee

Development Focus

Aisha owns the customer security questionnaires and trust-package responses that gate enterprise deals, splitting her time between compliance and third-party risk. She is the single point on a pipeline that the sales cycle depends on, and as deal volume grows her turnaround time has become a constraint on enterprise velocity (RISK-012).

Her growth thesis pairs load relief with expanded ownership. The near-term move is to convert a repetitive, manual workload into a curated, automated trust function (REC-011) — and in doing so, free herself to grow into the owner of Customer Trust as a program rather than a queue. She has the customer-facing fluency and the control knowledge to lead how Mutechs presents its security posture to enterprise buyers.

Year 1
Stand up an answer library and trust portal so questionnaires are answered from curated, reusable content rather than hand-built each time. Ties to REC-011 (automate questionnaire response) and P6 (Scale GRC).
Define and report questionnaire turnaround as a metric tied to enterprise deal velocity, making the bottleneck visible and managed. Ties to REC-016.
Cross-train with Felix Bauer on control evidence so trust responses are grounded in the live audit posture.
Year 2
Own Customer Trust as a program: a maintained trust center, proactive assurance content, and a model that scales with deal volume rather than headcount.
Deepen third-party risk skill alongside David Kim, building breadth across the two vendor-and-customer-facing lanes of GRC.
Develop the customer-facing security narrative for enterprise deals, partnering with sales on the highest-value reviews.
Training Plan — Aisha Bello · Year 3 & ContinuityMutechs · June 2026

GRC Analyst, Customer Trust · GRC · Permanent Employee

Year 3
Lead Customer Trust and security assurance as a named owner, with the answer library and trust portal carrying routine volume automatically.
Mentor a junior analyst into questionnaire operations, building the bench beneath her.
Cross-Training & Knowledge Continuity

Aisha is the single owner of the customer-questionnaire pipeline, and that pipeline touches revenue directly — continuity here protects deal velocity.

Build the answer library so questionnaire knowledge lives in shared, curated content, not only in Aisha's head; this is the continuity fix and the load relief at once.
Name a documented backup — Felix Bauer or David Kim — able to run questionnaire responses from the library during any absence.
Document the trust-portal workflow and escalation path in Confluence so customer commitments never stall on one person being unavailable.
Notable Quote
"Right now every questionnaire feels like I'm rewriting the same answers under a deadline. I want to build the library once, so the deals move faster and I get to do the work that actually needs me."

Context: The quote reveals that automation is both Aisha's relief from overload and her path to higher-value Customer Trust ownership — load relief and growth are the same move.

Training Plan — Andre Silva · Focus & Years 1–2Mutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Contractor — Arclight Talent

Development Focus

Andre is an Arclight Talent contractor and the most cloud-security-concentrated engineer on the team, carrying posture and remediation work alongside automation skill (Python, Tines, Terraform). His augmented capacity is real value, and it also represents a dependency: the work he does daily should not walk out the door when the engagement ends. His plan is built around knowledge transfer to permanent staff and reducing single-vendor reliance, in line with REC-017's intent to convert contractor capacity into durable in-house ownership.

For Andre himself, the development focus is to leave the team stronger than he found it: codify what he builds, mentor permanent engineers into it, and grow his own automation and CSPM range while the engagement runs.

Year 1
Document and hand off all cloud-posture and remediation workflows he owns, so a permanent engineer can run them without him. Ties to P4 (Cloud & Platform Guardrails).
Convert his automation work (Tines, Python) into shared, version-controlled tooling with a permanent owner, rather than scripts only he maintains.
Support the guardrail documentation effort (REC-003) by automating posture checks and evidence, transferring the patterns to Priscilla Adeyemi and Wei Zhang.
Year 2
Deepen CSPM and guardrails-as-code skill while pairing with permanent staff, so every advance he makes is mirrored by a teammate who stays.
Help bring the acquired Lumify cloud estate under core posture monitoring (REC-006) with Owen Bennett, documenting as he goes.
Training Plan — Andre Silva · Year 3 & ContinuityMutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Contractor — Arclight Talent

Year 3
Position the team for a clean transition: either conversion to a permanent seat (REC-017) or a complete handover with no capability lost, leaving automation and runbooks that outlast the contract.
Cross-Training & Knowledge Continuity

As a contractor, Andre's continuity plan is the inverse of a permanent teammate's: the goal is to ensure nothing critical depends on him, and to reduce single-vendor concentration on Arclight Talent across the team:

Require every workflow and automation he owns to be documented and paired with a permanent engineer who can run it solo.
Keep guardrail and CSPM authority with permanent staff (Wei, Priscilla); Andre augments and automates, and does not become a second informal single owner.
Use his engagement as the test case for REC-017 — measuring whether his work can be fully absorbed in-house, which is the evidence for converting contractor spend to a permanent hire.
Notable Quote
"I'm here to make myself unnecessary the right way — everything I build should still run the day my contract ends."

Context: Andre frames a contractor's success as leaving behind documented, owned capability rather than indispensability, which is exactly the knowledge-transfer posture that lowers single-vendor risk.

Training Plan — Anika Sharma · Focus & Years 1–2Mutechs · June 2026

IAM Engineer · Identity & Access · Contractor — Keystone Identity Partners

Development Focus

Anika carries the deepest hands-on identity-engineering and automation skill on the team: her competency mix is heavily Identity and Access Management (IAM) with a Security Engineering second, and she works in Python, Tines, and Terraform across the Okta and SailPoint stack. In practice she is the engine behind lifecycle automation and the access-review tooling. She is a Keystone contractor, which means the automation that keeps identity operations running is, like the rest of the team, held outside permanent staff (RISK-004).

Her development plan pairs continued technical growth with a clear knowledge-transfer mandate. Anika's automation work is the most transferable asset on the team — code and pipelines document themselves better than tacit operations knowledge does — and the goal is to make sure that as Mutechs builds permanent ownership, the automation comes with it rather than walking out the door with the vendor.

Year 1
Convert identity automation from working scripts into a documented, version-controlled, peer-reviewable codebase that permanent staff can read, run, and extend. Ties to P5 (Unify Identity) and REC-013.
Lead knowledge transfer of the lifecycle-automation and access-review tooling to Nadia Karim and incoming permanent engineers, with paired sessions and runbooks (REC-005, REC-013).
Deepen identity-as-code maturity — least-privilege automation and access-certification workflows — raising the platform beyond manual operation.
Year 2
Build the automation for the Lumify directory merge into core SSO (REC-006), pairing with permanent staff so the integration tooling is co-owned from the start.
Broaden into adjacent Security Engineering work that connects identity telemetry to detection and access reviews, widening her platform range.
Training Plan — Anika Sharma · Year 3 & ContinuityMutechs · June 2026

IAM Engineer · Identity & Access · Contractor — Keystone Identity Partners

Year 3
Trajectory toward a senior identity-automation or identity-engineering role — a strong candidate for the permanent conversion contemplated in REC-005 and REC-017, where her automation becomes an owned in-house capability.
Cross-Training & Knowledge Continuity

Anika is a single owner of the identity-automation layer, and as a contractor that concentration compounds RISK-004.

Make her automation codebase the documentation: enforce version control, peer review, and READMEs so the tooling is legible to permanent staff without her present.
Name a permanent engineer as the standing co-owner of the automation pipelines, with shadowing on every significant change (REC-013).
Record handover walkthroughs of the lifecycle and access-review automation before any contract roll-off, so identity operations continue uninterrupted.
Notable Quote
"Automation is the easy part to hand off — it's all in code. The hard part is making sure someone permanent actually reads it before I roll off."

Context: The quote reflects Anika's awareness that her contractor status, not her skill, is the continuity risk — and that her development is measured by how much of her automation becomes durable, owned capability.

Training Plan — Carlos Reyes · Focus & Years 1–2Mutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Development Focus

Carlos is the third Northbeam analyst on the outsourced tier-1 SOC, covering triage, SIEM and EDR monitoring, and escalation handling on Splunk, CrowdStrike, and Tines (RISK-009). His strength shows up under pressure: when an alert turns into something real, he is clear and calm about what he saw, what he did, and what the next responder needs. In a team where incident command is still informal and the tier-1/tier-2 hand-off is immature, that communication discipline is genuinely scarce.

Because Carlos is a contractor, this plan develops his tier-2 and incident-support capability while transferring his escalation craft into permanent staff, so Mutechs's response quality stops depending on a single vendor relationship (REC-010, REC-004).

Year 1
Standardize the escalation narrative he writes during live alerts into a reusable template, strengthening the formal tier-1/tier-2 hand-off. Ties to P2 (Detection & Response) and REC-010.
Build tier-2 investigation skills so he can scope and enrich an incident before escalating, not only flag it.
Support tabletop exercises as the tier-1 voice, helping the team pressure-test the new incident-command runbooks (REC-004).
Year 2
Train as a first responder under the incident-command charter, handling the early containment steps with clear communication into the permanent IR core.
Own escalation-quality and hand-off metrics from the tier-1 side, making the MDR relationship measurable.
Contribute recurring escalation themes back to detection tuning so noisy or low-value alerts get addressed at the source (REC-014).
Training Plan — Carlos Reyes · Year 3 & ContinuityMutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Year 3
Operate as a tier-2 analyst and incident first-responder, and a strong internal candidate if MDR spend converts to a permanent SOC seat (REC-017).
Mentor incoming analysts on incident communication and escalation discipline, embedding the practice in the team rather than the vendor.
Cross-Training & Knowledge Continuity

Carlos's continuity value is in making his escalation and communication craft a Mutechs asset before any Northbeam roster change.

Capture his escalation templates and incident-communication patterns in shared runbooks, so the practice survives a vendor transition.
Pair him with Hassan and Grace during live incidents so command and response context flows between the vendor and the permanent core (REC-004).
Build a permanent counterpart for the tier-1 communication role over time, reducing single-vendor dependency on response quality.
Notable Quote
"When an incident is moving fast, the win isn't speed — it's that the next person picks up exactly where I left off with no guessing. That hand-off is a skill, and it shouldn't walk out the door with a contract."

Context: The quote underscores Carlos's communication discipline and frames it as transferable, Mutechs-owned capability rather than vendor-bound routine.

Training Plan — Daniel Okafor · Focus & Years 1–2Mutechs · June 2026

Senior Manager, Cloud & Platform Security · Cloud & Platform Security · Permanent Employee

Development Focus

Daniel leads Cloud & Platform Security at a moment when the team's mandate is widening faster than its bench. His time today splits across program management, hands-on cloud security, and architecture, and he carries the team that owns the guardrails for the entire multi-tenant estate. His growth thesis is a move from strong team lead toward broader platform-security leadership: an operator who sets the cloud-security strategy, charters durable ownership, and represents platform risk at the leadership table rather than firefighting it.

The most pressing leadership test in front of him is structural, not technical. His team's IaC guardrails and CSPM rest on one engineer (Wei Zhang) with no documented backup (RISK-002). Daniel's development is inseparable from fixing that concentration: a leader is measured by whether the function survives any one person's absence, including his own.

Year 1
Own the execution of REC-003 personally: stand up documentation-as-code and runbooks for the guardrail and CSPM stack, and name a second owner (Priscilla Adeyemi is the natural candidate). Ties to P4 (Cloud & Platform Guardrails).
Build a capability-coverage map for the team so single-owner concentration is visible and managed, not discovered during an outage.
Sharpen executive communication: translate cloud posture into the business scorecard (platform uptime, audit readiness) for the governance cadence forming under P1.
Partner with Identity & Access to scope the Lumify integration owned informally by Owen Bennett (RISK-005), so a plan of record exists.
Year 2
Take chartered cross-team accountability for cloud-side vulnerability remediation as the operating model matures (REC-009), giving the team a clear seam with Security Engineering.
Develop people-leadership depth: formal career plans for all four of his engineers, succession mapping for every single-owner capability.
Grow architecture range beyond cloud into platform-wide secure-design standards, positioning the team as a guardrail authority across acquisitions.
Training Plan — Daniel Okafor · Year 3 & ContinuityMutechs · June 2026

Senior Manager, Cloud & Platform Security · Cloud & Platform Security · Permanent Employee

Year 3
Step into broader platform-security leadership: a Director-level remit spanning cloud, platform, and the integration of future acquired estates.
Mentor an emerging team lead so his own role is backed up, closing the key-person loop at the management layer.
Cross-Training & Knowledge Continuity

Daniel's continuity obligation runs in two directions. Downward, he must end the single-owner state of his most critical capability:

Name Priscilla Adeyemi as the documented backup to Wei Zhang and fund the shadowing time to make it real.
Require the guardrail and CSPM stack to be documented as code and runbooks, reviewed quarterly, so the knowledge lives in the repository, not one head.

Upward, his own role carries program knowledge and leadership-table context that no one else holds. Identifying and growing a deputy team lead is the succession-depth move that makes the team resilient at the management layer.

Notable Quote
"I can run the strongest cloud team here and still be one resignation away from losing our guardrails. That's not a Wei problem — that's my job to fix."

Context: Daniel frames key-person risk as a leadership responsibility rather than an individual's fault, which is exactly the reframe that turns a single-owner concentration into managed succession depth.

Training Plan — David Kim · Focus & Years 1–2Mutechs · June 2026

Third-Party Risk Analyst · GRC · Permanent Employee

Development Focus

David is the sole analyst on a nascent third-party risk program, with most of his time in third-party risk management and the balance in compliance. Mutechs depends on three security vendors — Northbeam, Arclight, and Keystone — and integrates acquired companies, yet there is no vendor tiering, assessment workflow, or mandatory pre-integration security review (RISK-011). The Lumify integration debt is the cautionary example of what unassessed risk becomes.

His growth thesis is program-building from the ground up. David has the chance few analysts get: to define a function rather than inherit one. The path forward moves him from running ad hoc vendor reviews to owning a chartered third-party risk program (REC-012) — tiering, workflow, and a pre-integration gate — that becomes durable Mutechs infrastructure under P7 (Third-Party Risk).

Year 1
Build a vendor tiering model and a risk-based assessment workflow in OneTrust and Whistic, starting with the three security vendors. Ties to REC-012 and P7 (Third-Party Risk).
Establish a mandatory pre-integration security review so the next acquisition does not repeat the Lumify debt. Ties to RISK-011 and RISK-005.
Cross-train with Aisha Bello on customer trust, since vendor assessments and customer questionnaires share evidence and tooling.
Year 2
Mature the program into continuous third-party monitoring with defined reassessment cadences by vendor tier.
Develop supply-chain risk depth — fourth-party exposure, SBOM awareness, and concentration risk across the vendor portfolio.
Report third-party risk posture into the governance cadence as a managed metric. Ties to REC-016.
Training Plan — David Kim · Year 3 & ContinuityMutechs · June 2026

Third-Party Risk Analyst · GRC · Permanent Employee

Year 3
Own third-party and supply-chain risk as an established program with a documented playbook, positioned to add an analyst as vendor volume grows.
Partner with M&A and procurement so security review is a standard gate in vendor onboarding and acquisitions.
Cross-Training & Knowledge Continuity

David is a single-analyst program, so continuity here is about turning a one-person effort into documented, transferable infrastructure as it is built.

Document the tiering model, assessment workflow, and pre-integration review as runbooks in Confluence from the start, so the program is the asset rather than David's memory of it.
Name a documented backup within GRC — Aisha Bello, given the shared OneTrust/Whistic tooling — able to run a vendor assessment during an absence.
Frame growth as succession depth: a program designed to be handed to a second analyst, not a role that only one person understands.
Notable Quote
"We brought Lumify in without a real security review and we're still paying for it. I want a tiering model and a gate in place so the next vendor or acquisition gets assessed before it's already inside the platform."

Context: The quote shows David framing his work as building durable program infrastructure, with the Lumify integration debt as the concrete lesson driving the pre-integration gate.

Training Plan — Devin Cole · Focus & Years 1–2Mutechs · June 2026

Application Security Engineer · Product Security · Contractor — Arclight Talent

Development Focus

Devin is an Arclight Talent contractor augmenting the application-security backlog, weighted heavily toward Application Security with a strong Vulnerability Threat Management line. He is productive and capable, and his presence reflects a structural pattern the roadmap intends to unwind: capability delivered through staff augmentation rather than durable in-house ownership. His development plan is therefore framed differently from the permanent team's — the priority is deliberate knowledge transfer to permanent staff and a path that reduces Product Security's dependence on a single contractor and a single vendor (REC-017).

The goal is not to grow Devin's tenure as a contractor indefinitely. It is to make his contribution durable: ensure the work he does outlives the engagement, and create an explicit decision point on converting the role to permanent or transitioning its knowledge to the permanent bench.

Year 1
Convert tacit knowledge into shared knowledge: document every AppSec workflow, triage decision, and recurring finding pattern in Confluence so a permanent teammate can carry the work. Ties to P3 (Embed Security in the SDLC) and the continuity intent of REC-013.
Pair-work the application-security backlog with Tomasz and Sofia so review and remediation skills land with permanent staff, not only with the contractor.
Establish a clear knowledge-transfer checklist with Lena that defines what "transferable" means for every recurring task Devin owns.
Year 2
Surface a conversion-or-transition decision: either convert this role to a permanent senior AppSec hire (the REC-017 net-zero swap) or formally hand its scope to permanent teammates with documented runbooks.
Cross-train permanent staff on the Vulnerability Threat Management slice (Tenable, Qualys) so that coverage does not leave with the contract.
Training Plan — Devin Cole · Year 3 & ContinuityMutechs · June 2026

Application Security Engineer · Product Security · Contractor — Arclight Talent

Year 3
If converted, follow the permanent senior-AppSec track. If transitioned, ensure a clean, documented exit with zero single-owner knowledge left behind and no capability gap created by departure.
Cross-Training & Knowledge Continuity

As a contractor, Devin is by definition a continuity risk: knowledge that leaves when the engagement ends, and a dependency on a single vendor (Arclight Talent). The continuity plan is the core of his plan, not an addendum:

Name a permanent backup — Tomasz for pipeline-adjacent work, Sofia for senior review — for every task Devin currently owns alone.
Maintain living runbooks and a contribution log so the permanent team can reconstruct his work without him.
Hold a standing monthly knowledge-transfer review with Lena to confirm transfer is actually happening, not deferred to an exit that arrives without warning.
Notable Quote
"I want to leave the team better than augmented — I'd rather hand over something documented and durable than be the person they can't afford to lose."

Context: The quote reframes the contractor relationship around continuity: Devin's success is measured by how little the team depends on him personally, directly serving the reduce-contractor-dependency intent of REC-017.

Training Plan — Felix Bauer · Focus & Years 1–2Mutechs · June 2026

Senior GRC Analyst · GRC · Permanent Employee

Development Focus

Felix is the deepest controls-and-evidence practitioner on the GRC team, with the majority of his time in compliance and a meaningful share in data protection and privacy. He already does the hands-on audit work — control implementation, evidence collection, and SOC 2 / ISO 27001 support — that the team's single owner currently has to supervise directly.

His growth thesis is a clear step up: from senior analyst to GRC lead and deputy to the director (REC-008). Mutechs' compliance scale rests on one overloaded owner (RISK-007), and the fastest way to relieve that load is to develop Felix into someone who can own an audit cycle end to end. He has the depth; the development is in breadth of ownership, audit leadership, and managing a calendar rather than a checklist.

Year 1
Take staged ownership of one full SOC 2 cycle — scoping, evidence, auditor coordination — with Hannah Weiss in a review role rather than driving. Ties to REC-008 and P6 (Scale GRC).
Lead the move to automated control evidence in Vanta and Drata, replacing manual collection across the bench. Ties to RISK-013.
Build audit-program management skill: managing the calendar, dependencies, and analyst assignments, not only executing controls.
Year 2
Own the ISO 27001 audit lead role as that scope expands alongside SOC 2, running execution while the director leads the function. Ties to P6 (Scale GRC).
Develop coaching capability by mentoring the junior analysts on evidence and control work.
Broaden into framework strategy — control mappings across SOC 2, ISO 27001, and customer commitments — to reduce duplicated effort.
Training Plan — Felix Bauer · Year 3 & ContinuityMutechs · June 2026

Senior GRC Analyst · GRC · Permanent Employee

Year 3
Operate as the established GRC deputy: able to run any audit through the director's absence, and a credible successor for the director seat.
Represent GRC in cross-team forums and enterprise assurance, carrying compliance into design conversations rather than after them.
Cross-Training & Knowledge Continuity

Felix is the designated continuity answer for the GRC single-owner risk, and his own growing knowledge needs the same protection.

Pair with Hannah Weiss on a documented audit-calendar handoff so the deputy role is real, not nominal.
Document control-evidence procedures and Vanta/Drata automation as runbooks so audit execution survives any single absence.
Cross-train with Rebecca Stone on privacy controls and with Aisha Bello on customer-trust evidence, so audit knowledge is shared across at least two people per control area.
Notable Quote
"I know these controls cold. The next thing I want to own isn't another checklist — it's the whole audit, start to finish, so it doesn't all sit on one person's calendar."

Context: The quote shows Felix is ready to move from execution to ownership, and that he sees stepping up as the way to de-risk the team, not just advance himself.

Training Plan — Grace Okonkwo · Focus & Years 1–2Mutechs · June 2026

Incident Response Analyst · Detection & Response · Permanent Employee

Development Focus

Grace is the incident-response depth on the team, with about 60% of her time in IR and the rest in security operations. Alongside Hassan, she is one of only two teammates carrying incident-response capability, which makes her both essential to live response and the natural candidate to grow into a formal IR leadership role (RISK-003). She handles triage, containment, post-incident review, and runbook work — the practitioner foundation that a chartered IR program will be built on.

The growth thesis is to develop Grace from a strong responder into a deputy incident commander and, over time, an IR leader in her own right, while broadening her into detection so she is not boxed into a single competency. Her path also helps de-risk the team's two largest concentrations: informal incident command and single-owner detection.

Year 1
Train as the standing deputy incident commander under the new incident-command charter, leading lower-severity incidents end to end under Hassan's review. Ties to P2 (Detection & Response) and REC-004.
Co-author the incident runbooks and severity definitions, converting her hands-on knowledge into the team's documented playbook.
Begin structured cross-training into detection engineering by shadowing Marcus on authoring and tuning (REC-002, REC-013).
Year 2
Take point as incident commander on a defined share of real incidents, building command judgment under genuine pressure.
Grow detection literacy into contribution — writing and reviewing a subset of detections — so the team has a second pair of hands on detection-as-code (REC-014).
Lead quarterly tabletop exercises, maturing the team's response muscle and the runbooks behind it.
Training Plan — Grace Okonkwo · Year 3 & ContinuityMutechs · June 2026

Incident Response Analyst · Detection & Response · Permanent Employee

Year 3
Step into a senior IR or detection-and-response role, owning the IR program's day-to-day and mentoring newer analysts.
Serve as a credible internal candidate for a tier-2 or lead position as the team converts outsourced coverage to permanent depth (REC-017).
Cross-Training & Knowledge Continuity

Grace is the linchpin of the team's continuity plan — she is the second owner that two single-person concentrations need.

Formalize her as deputy incident commander so incident command no longer rests on Hassan alone, with documented rotation and decision rights.
Build her detection cross-training as a real second-owner path for Marcus's work, not a familiarization exercise, with shared authoring and review responsibilities over time.
Ensure her own IR runbooks and post-incident templates are documented and shared, so her growing responsibilities do not create a new single point of knowledge.
Notable Quote
"I've run enough incidents to know the playbook in my head. The next step is getting it out of my head and into the team — and learning the detection side so I understand the alert before it ever pages me."

Context: The quote shows Grace's readiness to lead and her appetite to broaden into detection, which is exactly the cross-training the team needs to close two concentration risks at once.

Training Plan — Hannah Weiss · Focus & Years 1–2Mutechs · June 2026

Director, Governance Risk & Compliance · GRC · Permanent Employee

Development Focus

Hannah is the single owner of the SOC 2 and ISO 27001 audit calendar and the customer-questionnaire pipeline, carried against a thin analyst bench (RISK-007). Today her week is consumed by execution: collecting evidence, shepherding auditors, and absorbing escalations that a deputy would otherwise handle. That keeps her close to the controls and far from the work only she can do — designing a GRC function that scales with Mutechs' enterprise revenue.

Her growth thesis is a deliberate shift from operator to function-builder. The goal is a distributed GRC team where audit, privacy, customer trust, and third-party risk each have a named owner, and Hannah leads the program rather than running every line of it. This is both a development path and a continuity fix: her load is the organization's largest compliance risk, and relieving it is the precondition for everything else in P6 (Scale GRC).

Year 1
Stand up a deputy/lead structure by developing Felix Bauer toward an audit-lead role, transferring SOC 2 / ISO 27001 calendar ownership in stages. Ties to REC-008 (distribute the audit calendar).
Move from manual evidence collection toward automated control evidence in Vanta and Drata, freeing her time from the audit floor. Ties to P6 (Scale GRC).
Publish a documented RACI for the GRC team so audit, privacy, customer trust, and third-party risk each have a clear owner. Ties to P1 (Operating Model).
Year 2
Lead the ISO 27001 expansion as a repeatable program rather than a personal calendar, with the audit lead running day-to-day execution.
Build executive-facing GRC metrics — audit readiness, questionnaire turnaround, control coverage — tied to the governance cadence. Ties to REC-016.
Develop people-leadership depth: structured coaching, growth plans for each analyst, and succession for her own seat.
Training Plan — Hannah Weiss · Year 3 & ContinuityMutechs · June 2026

Director, Governance Risk & Compliance · GRC · Permanent Employee

Year 3
Operate as a true GRC function head: strategy, board-level trust narrative, and customer-facing assurance, with execution fully distributed across the bench.
Mentor the next director-level GRC leader and represent compliance in enterprise deal strategy.
Cross-Training & Knowledge Continuity

Hannah is the most concentrated single-owner risk in GRC, and continuity here protects enterprise revenue directly.

Name Felix Bauer as documented deputy for the audit calendar; transfer ownership of one full audit cycle to him within Year 1 with Hannah in a review role.
Document the audit calendar, evidence sources, and auditor relationships as runbooks in Confluence so no cycle depends on tacit knowledge in her head.
Distribute ownership: Aisha Bello for customer trust, David Kim for third-party risk, Rebecca Stone for privacy — each able to brief auditors in their lane.
Frame this as succession depth, not a stopgap: the target is a GRC function that runs a clean audit through any single absence.
Notable Quote
"I don't want to be the person every audit depends on. I want to build the team that makes the audit boring — predictable, evidenced, and owned by more than one calendar."

Context: The quote reveals Hannah's readiness to move from heroic single ownership to function-building, and her recognition that her own overload is the risk worth designing out.

Training Plan — Hassan Mahmoud · Focus & Years 1–2Mutechs · June 2026

Manager, Detection & Response · Detection & Response · Permanent Employee

Development Focus

Hassan runs Detection & Response and already carries incident command for the platform, just without a charter behind it (RISK-003). His time splits evenly across security operations and incident response, with a slice of program management — the profile of a working manager who still touches the keyboard during a real event. That hands-on instinct is an asset and, at the current scale of a multi-tenant SaaS platform, the team needs his authority formalized so the room knows who decides under pressure.

The growth thesis is to convert informal command into a defined operating discipline: published severities, named roles, escalation authority, and a managed vendor relationship with Northbeam. The aim is for Hassan to lead the function by design rather than improvisation, while building the bench depth that lets him step back from every incident.

Year 1
Charter the incident-command structure with defined severities, roles, and escalation authority; publish runbooks and stand up a quarterly tabletop cadence. Ties to P2 (Detection & Response) and REC-004.
Define the on-call rotation across the permanent core and the Northbeam analysts so coverage and hand-off are explicit, not assumed.
Begin formalizing the Northbeam MDR SLA, coverage hours, and tier-1/tier-2 escalation hand-off as a measured service (REC-010).
Year 2
Establish detection-coverage and response KPIs (mean time to contain, escalation accuracy, coverage map completeness) and report them into the governance cadence (REC-016).
Develop Grace Okonkwo as a deputy incident commander, distributing command depth across two people rather than one.
Lead the operational integration of a second detection engineer (REC-002) so the team's monitoring and engineering capacity scale together.
Training Plan — Hassan Mahmoud · Year 3 & ContinuityMutechs · June 2026

Manager, Detection & Response · Detection & Response · Permanent Employee

Year 3
Grow into a senior detection-and-response leader who owns a chartered IR program, a managed MDR partnership, and an internal SOC with genuine tier-2 depth.
Mentor the team's analysts toward permanent senior roles, reducing the function's reliance on outsourced tier-1 (REC-017).
Cross-Training & Knowledge Continuity

Hassan is the single holder of incident command, which is the continuity exposure to close first.

Document the incident-command playbook — severities, roles, decision rights — so command is a defined process any qualified responder can run, not tacit knowledge in one manager's head.
Name and train Grace Okonkwo as the standing deputy incident commander, with rotation so she leads live incidents under Hassan's review.
Capture escalation paths and vendor contacts in shared runbooks so a single absence never leaves an active incident without a clear commander.
Notable Quote
"Today, if something serious hits at 2 a.m., it works because people know to call me — not because we wrote down who's in charge. I want to fix that, because a process I can hand off is worth more than being the person everyone calls."

Context: The quote captures the gap between Hassan's reliable informal authority and the formalized, transferable command structure the platform now needs.

Training Plan — James Park · Focus & Years 1–2Mutechs · June 2026

IAM Analyst · Identity & Access · Contractor — Keystone Identity Partners

Development Focus

James runs the operational heart of identity governance: access reviews and joiner/mover/leaver operations, with a competency mix of Identity and Access Management (IAM) plus compliance. He works across Okta, SailPoint, and the audit tooling (Vanta, Drata), which puts him at the seam where identity meets the SOC 2 and ISO 27001 evidence the business depends on. He is a Keystone contractor, so the access-review and JML processes that produce audit evidence live, like the rest of the team, outside permanent ownership (RISK-004).

His development plan builds on a genuine advantage: his GRC second competency makes him the bridge between Identity & Access and the audit calendar. The path forward is to mature access reviews from a recurring task into a documented, automatable control, and to transfer that operational knowledge to permanent staff so the evidence pipeline does not depend on a contractor staying engaged.

Year 1
Document and standardize the JML and access-review processes into runbooks and control narratives that a permanent analyst can run unaided. Ties to P5 (Unify Identity) and REC-013.
Lead knowledge transfer of access-review operations to Nadia Karim and incoming permanent staff, with paired review cycles and a handover checklist (REC-005, REC-013).
Tighten the identity-to-audit evidence flow with the GRC team, making access-certification evidence cleaner and faster to produce ahead of SOC 2 / ISO 27001 cycles.
Year 2
Partner with Anika Sharma to move recurring access reviews toward automated certification, raising the work from manual to engineered and reducing review toil.
Support the Lumify directory merge by mapping and rationalizing legacy access ahead of the consolidation (REC-006), broadening his cross-stack range.
Training Plan — James Park · Year 3 & ContinuityMutechs · June 2026

IAM Analyst · Identity & Access · Contractor — Keystone Identity Partners

Year 3
Trajectory toward a senior identity-governance or IAM analyst-lead role bridging Identity and GRC — a candidate for the permanent ownership Mutechs is building toward under REC-005 and REC-017.
Cross-Training & Knowledge Continuity

James is the single operator of access reviews and JML, and as a contractor that makes the audit-evidence pipeline a continuity risk (RISK-004).

Convert the access-review and JML processes into documented runbooks and control narratives, so the evidence pipeline survives his roll-off (REC-013).
Name a permanent analyst — coordinating with the GRC bench — as the standing backup for access reviews, with shadowing across at least one full certification cycle.
Keep the identity-to-audit handoffs documented jointly with GRC, so access-certification knowledge is shared across two teams rather than held by one contractor.
Notable Quote
"Every access review I run is audit evidence — if I roll off mid-cycle and no one permanent knows the process, that's not just my problem, it's a SOC 2 problem."

Context: The quote ties James's contractor concentration directly to audit readiness, showing why his knowledge transfer matters beyond his own team and into the customer-trust commitments the business runs on.

Training Plan — Kofi Mensah · Focus & Years 1–2Mutechs · June 2026

Security Tooling Engineer · Security Engineering · Contractor — Arclight Talent

Development Focus

Kofi is the engineer who builds the automation the team runs on. His time concentrates in security tooling and automation, backed by working knowledge of vulnerability management, and he develops the integrations, telemetry pipelines, and workflow automation (Python, Tines, Terraform, GitHub) that turn repetitive security work into self-running systems. As an Arclight Talent contractor, he delivers high-value capability — and that capability presently lives in a single-vendor relationship.

His development plan is therefore framed around knowledge transfer and continuity rather than a multi-year career ladder inside Mutechs. The thesis is to make every system he builds outlive his engagement: owned, documented, and operable by permanent staff. The strongest outcome is the one REC-017 points to — that his proven value becomes the basis for a permanent tooling role, whether filled by conversion or by a permanent hire he has fully briefed.

Year 1
Build every automation as a documented, reviewed, permanently owned asset from the start: code in the shared repository, runbooks in Confluence, a named permanent owner per system. Ties to P1 (Operating Model) and REC-013.
Pair permanent engineers (Sarah Whitfield and Nina Castellanos) into the tooling work so no automation has a single contractor as its only operator.
Prioritize automations that relieve the program's manual load — remediation orchestration and KPI reporting — so the team's gains are structural, not tied to his presence.
Year 2
Transfer ownership of the core tooling platform to permanent staff with a documented hand-off, reducing single-vendor dependence (REC-017). Ties to P1 (Operating Model).
Extend automation patterns into adjacent teams — cloud remediation and detection workflows — while keeping each new system permanently owned. Supports the cloud-and-detection automation goals under P2 (Detection & Response) and P4 (Cloud & Platform Guardrails).
Mentor a permanent tooling engineer, should one be hired, as the durable owner of the platform he built.
Training Plan — Kofi Mensah · Year 3 & ContinuityMutechs · June 2026

Security Tooling Engineer · Security Engineering · Contractor — Arclight Talent

Year 3
Position the engagement to taper as permanent ownership matures: Arclight provides surge capacity rather than holding load-bearing knowledge.
If converted to permanent, grow into the team's senior tooling-and-automation engineer; if not, leave a fully documented, independently operable platform behind.
Cross-Training & Knowledge Continuity

Kofi is single-vendor, single-owner knowledge by default — the precise risk a contractor-built platform creates. Continuity is the central deliverable, not an afterthought:

Assign every automation a named permanent owner (Sarah or Nina) with documented code and runbooks, reviewed before each is considered done.
Schedule recurring pairing sessions so permanent engineers can modify and operate his systems, not merely run them.
Maintain a hand-off register of every tool, integration, and credential, so an Arclight transition or his departure does not strand the team's automation.
Notable Quote
"I'd call it a good month if something I built keeps running smoothly and nobody needs to call me about it. The goal is to make myself optional, not indispensable."

Context: Kofi treats permanent ownership as the measure of his own success, which is exactly the contractor posture that converts single-vendor dependence into durable in-house capability.

Training Plan — Lena Hoffmann · Focus & Years 1–2Mutechs · June 2026

Director, Product Security · Product Security · Permanent Employee

Development Focus

Lena leads central Product Security and carries the hardest brief on the roadmap: she is accountable for secure-by-design across every engineering squad, and she holds influence rather than authority over the embedded engineers who do the work. Her competency mix already spans Application Security, architecture and design, and program management, which is the right shape for the role. Her growth thesis is not more technical depth; it is converting a position of advice into a position of chartered authority and running Product Security as a program.

The development path centers on the reporting seam (RISK-006) and the operating-model work behind it. Lena's next two years are about designing and standing up a security-champion model with defined gates in the SDLC, then operating it with metrics the CISO and Engineering leaders both trust. The aim is for secure-by-design to become a requirement Mutechs engineers meet, not a recommendation Lena makes.

Year 1
Co-author the Product Security operating model with the CISO: the RACI for product versus central security, decision rights, and the chartered gate model. Ties to P3 (Embed Security in the SDLC) and directly to REC-007.
Build the influence-without-authority skill set deliberately: executive negotiation and a written secure-design standard that squads adopt because it is clear and low-friction, ahead of any solid-line change.
Define a small set of Product Security KPIs (design-review coverage, gate pass rate, finding remediation time) and bring them into the governance cadence (REC-016).
Year 2
Run the security-champion program at scale across squads; mature it from pilot to chartered function with named champions and an enablement curriculum.
Develop org-design and people-leadership range to manage a growing embedded team if the seam resolves toward a solid line.
Training Plan — Lena Hoffmann · Year 3 & ContinuityMutechs · June 2026

Director, Product Security · Product Security · Permanent Employee

Year 3
Grow toward a senior security-leadership trajectory (Senior Director / deputy-CISO scope), owning the full product-to-platform security model and mentoring the next layer of leaders.
Cross-Training & Knowledge Continuity

Lena is a single point of leadership for the entire product-security relationship with Engineering. To build succession depth:

Name Raj Patel as the standing technical deputy for design-review escalation and squad relationships, so the engineering relationship does not live solely with Lena.
Document the operating model, gate definitions, and squad map in Confluence as living artifacts, not personal knowledge.
Have Sofia Almeida co-lead a defined slice of the design-review portfolio to widen senior coverage.
Notable Quote
"I can review every design that comes to me, but I can't require the ones that never do. Give me the charter and I'll give you secure-by-design at scale."

Context: The quote captures the core of RISK-006 in Lena's own voice — her constraint is structural, not technical, and resolving the reporting seam is the unlock for P3.

Training Plan — Liam O'Brien · Focus & Years 1–2Mutechs · June 2026

IAM Engineer · Identity & Access · Contractor — Keystone Identity Partners

Development Focus

Liam is the de facto identity lead and architect at Mutechs, and he owns the core SSO platform. His competency mix — Identity and Access Management (IAM) paired with Architecture and Design — is the strongest on the team, and the organization runs on it. He is also a contractor, which makes him the human form of RISK-004: the single most important knowledge holder for the company's control plane has no permanent tie to it, and the IAM Architect seat he effectively fills is vacant on the org chart (REC-005).

His development plan is therefore unusual: it is built around making himself less indispensable. The most valuable thing Liam can do over the engagement is transfer what lives in his head into permanent ownership, while continuing to raise the platform's architectural maturity. Done well, that path also serves Liam — it is the strongest possible case for converting his role to a permanent senior seat, which REC-005 and REC-017 explicitly contemplate.

Year 1
Lead a structured knowledge-transfer program for the core SSO platform to Nadia Karim and incoming permanent staff: architecture records, runbooks, and recorded walkthroughs of SSO, federation, and lifecycle automation. Ties to P5 (Unify Identity) and REC-013.
Document the identity architecture as a living artifact in Confluence and Lucidchart, ending the state where the design exists only in his working memory.
Define the target identity architecture for the IAM Architect hire to execute against, so the vacant seat inherits a plan, not a mystery (REC-005).
Year 2
Architect the Lumify directory merge into core SSO as the technical design lead alongside Cloud & Platform Security (REC-006), pairing with permanent engineers throughout so the integration knowledge is shared as it is built.
Mature least-privilege, access certification, and federation patterns, raising the platform from operated to engineered.
Training Plan — Liam O'Brien · Year 3 & ContinuityMutechs · June 2026

IAM Engineer · Identity & Access · Contractor — Keystone Identity Partners

Year 3
Trajectory toward a permanent Principal / IAM Architect role at Mutechs, or — if he remains with Keystone — a deliberately reduced footprint where permanent staff own operations and he advises on architecture.
Cross-Training & Knowledge Continuity

Liam is the single highest-concentration knowledge holder on the team; his continuity plan is the team's continuity plan.

Treat knowledge transfer to permanent staff as his primary deliverable, with Nadia Karim and the future IAM Architect as named recipients and a tracked handover backlog.
Convert tacit SSO and federation knowledge into runbooks and architecture decision records before any contract roll-off, so the platform survives his departure (REC-013, REC-005).
Pair on every significant identity change with a permanent engineer, making shadowing the default operating mode rather than an exception.
Notable Quote
"I built most of what runs identity here, and that's exactly the problem — if I get hit by a bus, so does the login page. My job now is to make sure that's not true anymore."

Context: The quote captures RISK-004 from the inside — Liam understands his own concentration risk, and his development is measured by how much of his knowledge becomes permanent and shared.

Training Plan — Marcus Lindqvist · Focus & Years 1–2Mutechs · June 2026

Senior Detection Engineer · Detection & Response · Permanent Employee

Development Focus

Marcus is the sole detection engineer at Mutechs and authors and tunes virtually every detection that protects the multi-tenant platform (RISK-001). Detection engineering is roughly 70% of his time and almost none of anyone else's — a concentration that is simultaneously the team's deepest strength and its sharpest single point of failure (RISK-014). He clearly enjoys the craft: detection-as-code, threat hunting against cloud and identity telemetry, and coverage that keeps pace with a changing platform.

The growth thesis is to evolve Marcus from sole author into the technical lead of a detection practice. The goal is not to take work away from him; it is to make his work survivable and scalable — codified, peer-reviewed, and shared with a second engineer — so detection coverage no longer rises and falls with one person's availability.

Year 1
Mature the detection-as-code pipeline so detections live in version control with automated validation, moving coverage from hand-built artifacts to reviewable code. Ties to P2 (Detection & Response) and REC-014.
Build a documented coverage map across cloud and identity telemetry, making blind spots visible and prioritizable rather than implicit.
Partner with Hassan on onboarding a second detection engineer (REC-002), with Marcus defining the standards, review checklist, and ramp plan.
Year 2
Deepen cloud-native and identity-focused detection engineering for the multi-tenant estate, the most likely attack surface for the platform.
Establish and run a peer-review process for all new and changed detections, so no detection ships without a second set of eyes.
Grow threat-hunting from an individual activity into a repeatable, documented practice the wider team can execute.
Training Plan — Marcus Lindqvist · Year 3 & ContinuityMutechs · June 2026

Senior Detection Engineer · Detection & Response · Permanent Employee

Year 3
Step into a lead detection engineer role: owning detection strategy, mentoring a small detection function, and setting efficacy and coverage targets for the platform.
Drive automated detection validation and continuous coverage measurement so detection efficacy scales as code rather than as individual effort (REC-014).
Cross-Training & Knowledge Continuity

Marcus is the most acute key-person concentration in the team, and the continuity plan must be substantive, not a backup name on paper (REC-002, REC-013).

Add a second detection engineer as the primary structural fix, redirecting existing contractor spend toward a permanent senior hire where possible (REC-017). One engineer cannot be a backup to himself.
Move all detections into detection-as-code with version control and CI validation, so the logic, intent, and tuning history are captured in the repository rather than in Marcus's head.
Institute mandatory peer review on detections, building shared fluency across two engineers and creating a natural second owner.
Have Grace Okonkwo shadow detection authoring and tuning as a cross-training path, giving the IR side working literacy in how detections are built and why they fire.
Maintain runbooks for the detection pipeline (data sources, deployment, rollback) so the practice is operable during any absence.
Notable Quote
"I can write detections faster than I can write down how I write them — and that's exactly the problem. If I'm the only one who understands why a rule exists, then I'm not an asset, I'm a risk."

Context: The quote shows Marcus understands his own concentration risk and frames the fix as codifying and sharing his craft, not guarding it.

Training Plan — Mei Lin · Focus & Years 1–2Mutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Development Focus

Mei is a Northbeam analyst on the outsourced tier-1 SOC, working alert triage, SIEM and EDR monitoring, and escalations across Splunk, CrowdStrike, and Tines (RISK-009). Where some analysts route alerts, Mei tends to ask why a pattern keeps recurring — she has a hunter's curiosity about the signal underneath the queue. That instinct is exactly the raw material a maturing detection practice needs, and it is currently going untapped because tier-1 work is structured around volume rather than investigation.

Because Mei is a contractor, this plan grows her toward tier-2 and detection literacy while deliberately transferring the patterns she spots into permanent staff, so Mutechs builds durable capability instead of renting it (REC-010, REC-014).

Year 1
Channel recurring-alert observations into structured feedback for Marcus's detection-coverage map, turning queue noise into coverage signal. Ties to P2 (Detection & Response) and REC-014.
Develop tier-2 investigation depth — scoping and corroborating alerts across telemetry rather than triaging in isolation.
Help shape the tier-1/tier-2 hand-off documentation so escalations carry the investigative context she gathers (REC-010).
Year 2
Begin detection literacy: shadow Marcus to understand how detections are authored and tuned, and learn to read detection-as-code rather than only its alerts.
Lead a recurring false-positive review, feeding tuning recommendations back into the detection pipeline.
Contribute to threat-hunting hypotheses against cloud and identity telemetry, the platform's likeliest attack surface.
Training Plan — Mei Lin · Year 3 & ContinuityMutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Year 3
Grow into a tier-2 / detection-curious analyst and a strong internal candidate if Northbeam capacity converts to a permanent role (REC-017).
Help onboard new analysts into the hunting and tuning mindset, spreading the practice beyond any single person.
Cross-Training & Knowledge Continuity

Mei's continuity contribution is converting her pattern recognition into shared, Mutechs-owned knowledge before any vendor change.

Document the recurring-alert patterns and tuning insights she surfaces, so they live in the detection repository rather than in a contractor's memory.
Pair her detection shadowing with Marcus so coverage knowledge is shared across more than one person (REC-002).
Route her hunting hypotheses through the permanent team, keeping the analytic value with the platform and reducing single-vendor dependency on monitoring quality.
Notable Quote
"After you see the same alert fire fifty times, you stop asking 'is this bad' and start asking 'why does this keep happening' — that question is where the real detections come from."

Context: The quote captures Mei's investigative curiosity and points to where she adds the most lasting value: feeding the detection practice rather than just clearing the queue.

Training Plan — Nadia Karim · Focus & Years 1–2Mutechs · June 2026

Manager, Identity & Access · Identity & Access · Permanent Employee

Development Focus

Nadia is the only permanent teammate in Identity & Access, and she manages a bench that is entirely contracted to Keystone Identity Partners (RISK-004). Identity is the control plane for every system at Mutechs, and today its permanent ownership begins and ends with her. Her competency mix — Identity and Access Management (IAM) paired with program management — is exactly the right shape for the role she needs to grow into: the durable in-house owner of the identity platform, not the coordinator of a vendor that runs it.

Her growth thesis is to convert a managed-vendor relationship into owned in-house capability. That means deepening her own hands-on identity engineering enough to direct architecture decisions with authority, and standing up the permanent team around her — the vacant IAM Architect seat and a converted senior engineer (REC-005). The path forward is less about new breadth and more about turning Nadia into the person who can answer for the identity fabric when no contractor is in the room.

Year 1
Take direct ownership of the identity architecture decisions currently held by the de facto contractor lead: SSO design, lifecycle automation logic, and the access-review model. Shadow the core SSO platform until she can operate and explain it unaided. Ties to P5 (Unify Identity) and REC-005.
Lead the hiring and onboarding of the IAM Architect, and the conversion of one Keystone engineer to permanent, as the hiring manager who defines the durable team shape (REC-005, REC-017).
Build a documented identity runbook and architecture record so platform knowledge lives in Confluence, not in a contractor's head (REC-013).
Year 2
Grow the permanent team into a functioning unit: define roles, raise least-privilege and access-review maturity, and reduce Keystone to surge delivery rather than core operation.
Lead the Lumify identity-directory merge into core SSO as owner of record alongside Cloud & Platform Security (REC-006), deepening her architecture range.
Training Plan — Nadia Karim · Year 3 & ContinuityMutechs · June 2026

Manager, Identity & Access · Identity & Access · Permanent Employee

Year 3
Trajectory toward Senior Manager or Director, Identity, owning identity strategy across the core and acquired stacks and mentoring the architect and engineers seated beneath her.
Cross-Training & Knowledge Continuity

Nadia is a single point of permanent ownership for the entire identity platform — and the engineering knowledge sits with contractors below her, which inverts the usual continuity problem. To build succession depth:

Make knowledge transfer from the Keystone team to permanent staff a contractual deliverable, not a favor: documented runbooks, recorded walkthroughs, and a session-by-session handover plan for the SSO platform.
Seat the IAM Architect and a converted permanent engineer as the standing in-house backups for SSO, lifecycle, and access reviews, so no single contractor departure strands the platform.
Cross-train with Owen Bennett on the Lumify directory ahead of the merge, so acquisition identity knowledge has a second owner before integration.
Notable Quote
"I manage the identity platform, but right now I don't own it — three people who could roll off next quarter do. My job this year is to change that."

Context: The quote names RISK-004 plainly in Nadia's voice — her development is inseparable from building permanent ownership of the control plane the whole company depends on.

Training Plan — Nina Castellanos · Focus & Years 1–2Mutechs · June 2026

Security Engineer, Vulnerability Management · Security Engineering · Permanent Employee

Development Focus

Nina is the team's growth engine. Her time splits between vulnerability remediation engineering and cloud security, which makes her the natural bridge between the vulnerability-management program and the multi-tenant cloud estate it has to cover. She already works across Tenable, Qualys, Wiz, AWS, Kubernetes, and Terraform — the exact toolset that connects remediation to where the platform's risk actually lives.

Her growth thesis is to deepen on two fronts at once: become the program's strongest cloud-vulnerability engineer and grow into automation so remediation scales as code rather than as manual effort. That combination positions her as the documented second owner the vulnerability-management program has never had, and as a credible future cloud-security engineer if her interests pull that way.

Year 1
Become the cloud-vulnerability specialist for the program: own remediation across the multi-tenant AWS and Kubernetes estate, mapping findings to owners. Ties to P4 (Cloud & Platform Guardrails).
Grow automation depth with the team's stack (Python, Tines) so remediation orchestration and reporting move from manual to engineered.
Begin shadowing Sarah Whitfield on program prioritization and KPI definitions, stepping toward the documented-backup role (REC-013).
Year 2
Take ownership of cloud-native remediation workflows end to end, partnering with Cloud & Platform Security on container and Kubernetes findings. Ties to P4 (Cloud & Platform Guardrails) and the cloud-automation goals under P2 (Detection & Response).
Build detection-adjacent automation range — turning recurring remediation patterns into reusable guardrails and validation, contributing to the detection-as-code direction (REC-014).
Serve as the program's confirmed second owner with the documentation and access to run it in Sarah's absence.
Training Plan — Nina Castellanos · Year 3 & ContinuityMutechs · June 2026

Security Engineer, Vulnerability Management · Security Engineering · Permanent Employee

Year 3
Grow toward a senior security-engineering role: either as the cloud-and-automation depth behind the vulnerability program or as a move into Cloud & Platform Security, where her profile is a strong fit.
Mentor the next engineer joining the team, extending the bench she helped build.
Cross-Training & Knowledge Continuity

Nina's continuity value is what makes her development urgent: she is the planned second owner for a program that currently rests on one person (RISK-008). To make that real:

Formalize her as the documented backup to Sarah Whitfield, with shadowing time funded, not assumed.
Cross-train with Priscilla Adeyemi in Cloud & Platform Security on container and CSPM remediation, so cloud-vulnerability knowledge spans two teams rather than living in one seam.
Capture her remediation automations in the shared, owned tooling repository so they survive any single departure.
Notable Quote
"Half the vulnerabilities I chase live in the cloud, so I'd rather fix them once in Terraform than re-open the same ticket every scan. Automating the boring part is how I get to grow."

Context: Nina ties her own development to the program's resilience — her growth in cloud and automation is also the move that gives vulnerability management its missing second owner.

Training Plan — Owen Bennett · Focus & Years 1–2Mutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Development Focus

Owen joined through the Lumify acquisition and is the only person who understands its still-separate cloud organization and unmerged identity directory, which he maintains informally eighteen months on (RISK-005). His cloud-security depth is paired with real identity-and-access range (Okta, Active Directory, SailPoint), an unusual blend on this team that makes him the bridge between the acquired estate and the core platform.

His growth thesis has two strands. Near term, he is the continuity owner of acquisition knowledge that currently lives nowhere else; that knowledge must be documented and transferred before it integrates away. Longer term, his cloud-plus-identity range positions him to grow into a platform-security engineer who specializes in integrating acquired stacks — turning a one-off informal burden into a repeatable capability the company will need again.

Year 1
Document the Lumify cloud organization and identity directory as the owner of record: architecture, accounts, trust relationships, and the directory's mapping to core identity. Ties to P4 (Cloud & Platform Guardrails) and P5 (Unify Identity).
Partner with Identity & Access on the directory-merge plan (REC-006), making the unmerged SSO a chartered project rather than informal upkeep.
Bring the Lumify cloud estate under the team's core guardrails alongside Wei Zhang and Priscilla Adeyemi, so it stops being a coverage seam outside CSPM.
Year 2
Lead the execution of the Lumify identity merge into core SSO with Identity & Access, retiring the parallel directory and closing the seam an attacker could exploit.
Build cloud-security guardrail depth so his contribution outlasts the Lumify work and he is a full second or third hand on the core stack.
Formalize a reusable pre-integration security pattern from the Lumify lessons, feeding the third-party and acquisition review program (P7, REC-012).
Training Plan — Owen Bennett · Year 3 & ContinuityMutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Year 3
Become the team's go-to integration engineer for future acquisitions: the person who brings a new estate under core guardrails and identity by design, not years later.
Contribute to platform-security architecture spanning core and acquired environments.
Cross-Training & Knowledge Continuity

Owen holds acquisition knowledge as a sole informal owner, and the continuity goal is to integrate it out of existence while it is captured — succession depth through documentation and a real merge plan, not knowledge held hostage:

Assign Owen as the documented owner of record for the Lumify estate and require its architecture and identity mapping to be written down before integration work begins.
Pair him with Identity & Access (Nadia Karim's team) on the merge so the directory knowledge transfers to permanent identity ownership, not just to a wiki page.
As the Lumify cloud estate folds under core guardrails, ensure Wei and Priscilla can operate it, so no second informal owner replaces the first.
Notable Quote
"Lumify still runs because I remember how it's wired. The win isn't me documenting it forever — it's the day the directory is merged and there's nothing separate left to own."

Context: Owen treats integration, not preservation, as the goal, which reframes his unique knowledge from a personal continuity risk into a project with a finish line.

Training Plan — Priscilla Adeyemi · Focus & Years 1–2Mutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Development Focus

Priscilla owns container and Kubernetes security and cloud vulnerability remediation, with strong cloud-security depth and a working command of the same toolset (AWS, Wiz, Kubernetes, Terraform) that the team's guardrails run on. That overlap makes her the natural candidate to become the documented backup to Wei Zhang's IaC guardrail and CSPM stack — the team's most critical single-owner capability (RISK-002).

Her growth thesis is to broaden from container specialist toward a full-stack cloud-security engineer who can author and enforce guardrails as code, not only remediate findings. Stepping into the backup role is the fastest path to that breadth: it gives her ownership of the policy layer that decides what "secure" means across the estate, while closing the team's highest-severity concentration risk.

Year 1
Become the named, documented backup to Wei under REC-003: shadow guardrail changes and posture remediation, then run them solo from the runbooks. Ties to P4 (Cloud & Platform Guardrails).
Deepen guardrails-as-code fluency — Terraform policy, OPA, and CSPM (Wiz) configuration — moving from consuming policy to authoring it.
Formalize the container/Kubernetes security baseline she already owns into documented standards the whole team can apply.
Year 2
Co-own the guardrail and CSPM stack with Wei through a real on-call rotation, so the capability has two genuine owners rather than one and a name on a page.
Extend Kubernetes-security depth into the acquired Lumify cloud estate as it comes under core guardrails (REC-006).
Pursue a Kubernetes or cloud-security certification to anchor the broadening skill set.
Training Plan — Priscilla Adeyemi · Year 3 & ContinuityMutechs · June 2026

Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Year 3
Operate as a senior cloud-security engineer with shared architecture authority over the guardrail model, and begin mentoring the next backup so the bench keeps deepening.
Take a lead role in container-native detection and posture coverage in partnership with Detection & Response (P2, REC-014).
Cross-Training & Knowledge Continuity

Priscilla is the continuity solution for the team's top risk, and her own specialty needs the same treatment so backing up Wei does not create a new single-owner gap behind her:

Document the container and Kubernetes security baseline as code and runbooks, with Andre Silva or Owen Bennett able to cover remediation in her absence.
Treat her backup role for Wei as a scheduled, funded commitment — paired work and rotation — rather than something squeezed in around the day job.
Notable Quote
"I've been the one fixing what the guardrails flag. Owning the guardrails themselves is the part I actually want — and it means we stop having one person who can touch them."

Context: Priscilla wants the stretch into policy ownership, which aligns her career ambition exactly with the team's need for a second guardrails owner and makes the backup designation real rather than nominal.

Training Plan — Raj Patel · Focus & Years 1–2Mutechs · June 2026

Staff Product Security Engineer · Product Security · Permanent Employee

Development Focus

Raj is the seam personified. He sits embedded in the core platform engineering squad, reports into Product Security, and carries a dotted line to Engineering — the exact structure RISK-006 describes. That position is also his greatest asset: he is trusted inside the squad and fluent across Application Security, DevSecOps, and architecture and design. His growth thesis is to turn proximity into a repeatable model — to become the engineer who proves that embedded security raises velocity rather than slowing it, and whose pattern other squads adopt.

The path forward grows Raj from a strong embedded engineer into the technical anchor of the security-champion model. As Lena charters gates in the SDLC, Raj is the person who makes those gates real in CI/CD and shows squads they are workable.

Year 1
Become the reference implementer for the chartered gate model: secure-design templates, threat-modeling cadence, and CI/CD security gates that the core squad runs without friction. Ties to P3 (Embed Security in the SDLC) and REC-007.
Deepen architecture and design toward platform-level secure-design ownership for new multi-tenant capabilities.
Help define the product-security KPIs from the squad side so the metrics reflect what engineers actually experience (REC-016).
Year 2
Mentor and onboard champions across additional squads, codifying the embedded-engineer playbook so the model is reproducible rather than personal to Raj.
Broaden into supply-chain and pipeline integrity (SBOM, provenance) as platform risk grows.
Training Plan — Raj Patel · Year 3 & ContinuityMutechs · June 2026

Staff Product Security Engineer · Product Security · Permanent Employee

Year 3
Grow toward Principal Product Security Engineer: the org-wide technical authority on secure-by-design, and Lena's standing technical deputy for the Engineering relationship.
Cross-Training & Knowledge Continuity

Raj holds the institutional relationship with the core platform squad and the working knowledge of its design. That is single-owner knowledge in a structurally fragile seam. To build succession depth:

Document the embedded-engineer playbook — squad map, recurring design patterns, gate configurations — in Confluence as the template for future champions.
Pair Tomasz Kowalski on pipeline-gate work so a second engineer can carry CI/CD security in Raj's absence.
Establish a defined hand-off and shared on-call understanding with Engineering so the dotted line has a documented backup, not a single trusted individual.
Notable Quote
"I'm in the standups, so security gets asked about before the code is written — not flagged after it ships. That only scales if it's a model, not just me being in the room."

Context: Raj sees that his value is the embedded position itself; the development goal is to convert that into a chartered, reproducible champion model rather than a dependency on one well-liked engineer.

Training Plan — Ravi Anand · Focus & Years 1–2Mutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Development Focus

Ravi is one of three Northbeam analysts delivering Mutechs' tier-1 SOC entirely through the MDR vendor (RISK-009). His time is fully in security operations — alert triage, SIEM and EDR monitoring, and escalation handling on Splunk, CrowdStrike, and Tines. He is steady and process-minded, the kind of analyst who notices when a hand-off is ambiguous and writes it down. That instinct is valuable precisely because the tier-1/tier-2 hand-off between Northbeam and the permanent core is not yet formalized.

Because Ravi is a contractor, this plan is built around two outcomes: growing his tier-2 capability, and transferring the operational knowledge he accumulates into permanent staff so Mutechs reduces its dependence on the MDR vendor over time (REC-010, REC-017).

Year 1
Document the tier-1 triage and escalation workflow he runs daily, feeding directly into the formalized MDR SLA and tier-1/tier-2 hand-off. Ties to P2 (Detection & Response) and REC-010.
Build tier-2 investigation skills — pivoting across SIEM and EDR to scope an alert rather than only routing it.
Pair with Grace on escalations so investigative context transfers cleanly from Northbeam to the permanent IR core.
Year 2
Use his Tines fluency to help automate repetitive triage steps, capturing the automation logic in shared, Mutechs-owned playbooks rather than vendor-only knowledge.
Take ownership of escalation-quality metrics, helping make the MDR relationship measurable rather than assumed.
Contribute coverage-gap observations from the alert queue back to Marcus's detection-coverage map (REC-014).
Training Plan — Ravi Anand · Year 3 & ContinuityMutechs · June 2026

SOC Analyst · Detection & Response · Contractor — Northbeam Security

Year 3
Operate as a credible tier-2 analyst and a reference candidate should Mutechs convert MDR spend into a permanent SOC role (REC-017).
Mentor incoming tier-1 analysts on the documented Mutechs workflow, so onboarding no longer depends on tribal vendor knowledge.
Cross-Training & Knowledge Continuity

As outsourced tier-1, Ravi's continuity value is in moving what he knows into Mutechs before any vendor change.

Capture his triage and escalation workflow in Mutechs-owned runbooks, so the operating knowledge stays with the platform if the Northbeam roster turns over.
Pair tier-1 escalations with the permanent IR core (Grace, Hassan) so investigative context is shared, not siloed in the vendor.
Build a second internal touchpoint for every recurring playbook he authors, reducing single-vendor dependency on the monitoring function (REC-010).
Notable Quote
"I can see the gap the moment an alert crosses from us to the internal team — half the time the context doesn't travel with it. Writing that hand-off down properly is the most useful thing I can leave behind."

Context: The quote highlights Ravi's process discipline and frames his contribution as durable, Mutechs-owned knowledge rather than vendor-locked routine.

Training Plan — Rebecca Stone · Focus & Years 1–2Mutechs · June 2026

Compliance Analyst, Privacy · GRC · Permanent Employee

Development Focus

Rebecca carries the privacy and data-protection work for Mutechs, with her time split evenly between Privacy Analysis and compliance. She handles data classification and retention, DLP and privacy controls, and regulatory mapping across GDPR and CCPA — the privacy backbone that enterprise customers increasingly demand as a condition of sale.

Her growth thesis is ownership of privacy as a named program. Today privacy is one analyst's responsibility woven into a thin GRC bench; the path forward grows Rebecca into the clear owner of Mutechs' privacy posture, with the authority and structure to scale it alongside the SOC 2 / ISO 27001 program under P6 (Scale GRC). She has the regulatory fluency; the development is in program design, customer-facing privacy assurance, and depth as the team distributes ownership.

Year 1
Formalize a privacy program: a maintained data inventory, retention schedules, and a documented control set mapped to GDPR and CCPA in OneTrust and BigID. Ties to P6 (Scale GRC).
Take named ownership of privacy controls within the SOC 2 / ISO 27001 audit, partnering with Felix Bauer as the audit calendar distributes. Ties to REC-008.
Cross-train with Felix on control evidence so privacy and core compliance reinforce one another.
Year 2
Own privacy-by-design reviews for new platform capabilities, bringing data protection into product decisions earlier.
Develop customer-facing privacy assurance — DPAs, sub-processor transparency, and privacy content in the trust package — alongside Aisha Bello's Customer Trust work.
Deepen regulatory breadth beyond GDPR/CCPA as Mutechs' enterprise footprint expands.
Training Plan — Rebecca Stone · Year 3 & ContinuityMutechs · June 2026

Compliance Analyst, Privacy · GRC · Permanent Employee

Year 3
Lead privacy and data protection as an established program owner, positioned for a privacy lead or DPO-track role as the function scales.
Mentor an analyst into privacy operations and represent data protection in enterprise deal and product strategy.
Cross-Training & Knowledge Continuity

Privacy currently rests on Rebecca alone; building the program is also how that knowledge becomes shared and durable.

Document the data inventory, retention schedules, and regulatory mappings as runbooks in Confluence so privacy posture is transferable, not held in one analyst's recall.
Cross-train with Felix Bauer so a second teammate can speak to privacy controls during an audit or an absence.
Frame growth as succession depth: a privacy program designed to onboard a second owner as the team distributes the GRC bench under REC-008.
Notable Quote
"Customers ask harder privacy questions every quarter. I want our privacy posture to be a real program I own and can show, not something I'm reconstructing from memory each time an auditor or a deal asks."

Context: The quote reveals Rebecca's drive to turn distributed privacy work into an owned, documented program, tying her own growth to the customer-trust commitments that gate enterprise revenue.

Training Plan — Sarah Whitfield · Focus & Years 1–2Mutechs · June 2026

Senior Security Engineer, Vulnerability Management · Security Engineering · Permanent Employee

Development Focus

Sarah owns the vulnerability-management program in practice today. Her time concentrates in vulnerability management, backed by real strength in security tooling and automation, and she runs asset discovery, risk-based prioritization, remediation orchestration, and the MTTR and aging KPIs. The gap between what she does and the authority she holds is the heart of her story: her coverage spans Security Engineering, Cloud & Platform Security, and Product Security, while she has no cross-team mandate to require remediation outside her own team (RISK-008).

Her growth thesis is the most direct in the organization — become the chartered vulnerability-management program owner that REC-009 calls for. The development work is to grow from a strong senior engineer who manages the program informally into a recognized program owner who sets remediation SLAs, consolidates KPIs across teams, and is accountable for platform-wide vulnerability posture by mandate, not by goodwill.

Year 1
Step into the chartered VM program-owner role as the operating model lands: consolidate aging, MTTR, and SLA reporting into one cross-team view spanning Security Engineering, Cloud, and Product Security (REC-009). Ties to P1 (Operating Model).
Build the influence range the role needs: present remediation metrics in the governance cadence and negotiate SLAs with team leads rather than chasing fixes engineer to engineer.
Automate the program's reporting pipeline with the team's tooling stack so KPIs are generated, not hand-assembled.
Year 2
Extend the program into the SDLC seam: define how vulnerabilities found in product and pipeline are triaged and owned, working the boundary with Product Security (REC-009). Ties to P3 (Embed Security in the SDLC).
Deepen cloud-vulnerability range so the program covers the multi-tenant estate credibly, partnering with Cloud & Platform Security.
Mentor Nina Castellanos as the program's second owner, building the bench the role has never had.
Training Plan — Sarah Whitfield · Year 3 & ContinuityMutechs · June 2026

Senior Security Engineer, Vulnerability Management · Security Engineering · Permanent Employee

Year 3
Grow toward a lead or staff-level program role: the org-wide authority on vulnerability posture, with the program running as a managed service rather than a personal effort.
Develop the management option — formal program leadership — if that path appeals as the team scales.
Cross-Training & Knowledge Continuity

Sarah is a single owner of the working knowledge that holds the vulnerability-management program together — the asset inventory logic, prioritization model, and remediation relationships across three teams. That is exactly the concentration RISK-008 and REC-013 flag. To build succession depth:

Document the program of record — scope, SLAs, KPI definitions, and the cross-team remediation workflow — in Confluence so the program survives her absence.
Name Nina Castellanos as the documented backup and fund shadowing time on prioritization and reporting.
Move the program's automations out of personal scripts into the shared, owned tooling repository so continuity lives in code.
Notable Quote
"I'm accountable for vulnerabilities I can't actually make anyone fix. Give me the charter, and I'll give you a program — not a spreadsheet I babysit."

Context: Sarah names the authority gap precisely; her development goal is to convert the program she already runs informally into a chartered role with the mandate to match the responsibility.

Training Plan — Sofia Almeida · Focus & Years 1–2Mutechs · June 2026

Senior Application Security Engineer · Product Security · Permanent Employee

Development Focus

Sofia carries the deepest pure Application Security weight on the team, paired with a genuine offensive-security interest — secure-code review and threat modeling at 60% of her time, with a standing line in Penetration Testing and pipeline work alongside. Her growth thesis is to formalize the offensive track she is already drawn to and become Mutechs' internal adversary: the engineer who validates that the secure-by-design controls the team builds actually hold up against attack.

The path forward sharpens her offensive depth from periodic testing into a structured capability, while keeping her AppSec mastery as the foundation. As Product Security charters gates under P3, Sofia is the teammate who proves those gates work by trying to break past them.

Year 1
Stand up a recurring internal application and cloud penetration-testing cadence against the multi-tenant platform, with findings feeding the secure-design gates. Ties to P3 (Embed Security in the SDLC).
Pursue a recognized offensive credential (OSCP or equivalent) to formalize the pentest track and set the bar for assessment quality.
Co-lead a defined slice of Lena's design-review portfolio to widen senior AppSec coverage (see Lena's continuity plan).
Year 2
Build a purple-team practice with Detection & Response: run controlled offensive exercises that validate and improve Marcus Lindqvist's detection coverage, connecting P3 to P2 (Detection & Response).
Mentor Tomasz and Devin on threat-modeling depth, raising the floor of AppSec review across the team.
Training Plan — Sofia Almeida · Year 3 & ContinuityMutechs · June 2026

Senior Application Security Engineer · Product Security · Permanent Employee

Year 3
Grow toward Staff/Principal AppSec or a dedicated offensive-security lead role, owning the org's adversarial-testing program end to end.
Cross-Training & Knowledge Continuity

Sofia is the only teammate with meaningful offensive-security depth, which makes that capability a single-owner concentration as it grows. To build succession depth:

Document testing methodology, tooling (Burp Suite, Metasploit, Kali), and scoping standards as runbooks so assessments are repeatable by another engineer.
Cross-train Tomasz on baseline application testing so first-line pentest coverage survives her absence.
Keep her senior AppSec review knowledge shared with Raj and Tomasz so design-review depth is not concentrated in one person.
Notable Quote
"I'd rather find the path into our platform myself, on a Tuesday, than read about it in a customer's incident report. Give me the time to do it properly and I'll keep us ahead of it."

Context: Sofia's offensive instinct is a retention and capability opportunity — formalizing the pentest track gives her a development path the survey says most teammates lack, and gives Mutechs adversarial validation of its secure-by-design work.

Training Plan — Theo Brandt · Focus & Years 1–2Mutechs · June 2026

Security Program Manager · Security Leadership · Permanent Employee

Development Focus

Theo runs the roadmap and the program-management function for the whole security organization, reporting directly to the CISO. His competency mix — program management with a compliance second — makes him the connective tissue across seven teams that, after rapid growth, still carry overlapping ownership and no standing governance cadence (RISK-010). He is the person best positioned to operationalize the operating-model work that anchors P1.

His growth thesis is a move from coordinator to program leader. Today Theo plans the roadmap and chases cross-team coordination; the path forward is for him to own the governance cadence, the RACI, and the metrics that make the roadmap executable — the machinery behind REC-001 and REC-016 — and to build the security-leadership range that lets him steer the program, not just track it.

Year 1
Co-build and then run the governance cadence behind the security operating model: the cross-team forum, the RACI for shared work, and the decision-rights documentation. Ties to P1 (Operating Model) and REC-001.
Stand up the security metrics and reporting layer — detection coverage, vulnerability aging/MTTR, audit readiness, questionnaire turnaround — and bring it into the cadence so leadership steers by evidence (REC-016).
Deepen GRC fluency enough to track the SOC 2 / ISO 27001 audit calendar as a program, giving the overloaded GRC director a coordination partner (supports REC-008).
Year 2
Own the roadmap-to-execution loop end to end: dependency management across the recommendations, quarterly business reviews, and the career-and-retention framework rollout (REC-015) as a program Theo runs.
Build people- and influence-leadership range — driving outcomes across teams he does not manage — as preparation for a leadership seat.
Training Plan — Theo Brandt · Year 3 & ContinuityMutechs · June 2026

Security Program Manager · Security Leadership · Permanent Employee

Year 3
Trajectory toward a security program leadership role — Head of Security PMO or Chief of Staff to the CISO — owning the operating model and governance for the full organization and mentoring the next program managers.
Cross-Training & Knowledge Continuity

Theo is the single permanent program manager for the entire security organization; if he is unavailable, the governance cadence and roadmap tracking have no second owner.

Document the operating model, RACI, governance cadence, and metrics definitions as living artifacts in Confluence, so the program runs from shared records rather than Theo's working knowledge (REC-001, REC-016).
Name a deputy from among the team managers — coordinating with the CISO — to chair the governance forum when Theo is out, keeping the cadence uninterrupted.
Cross-train with the GRC team on the audit-calendar program so roadmap-to-audit coordination has a second informed owner.
Notable Quote
"I can track the roadmap all day, but tracking isn't governing. The job this year is to give every shared piece of work one owner and one forum that actually decides."

Context: The quote frames Theo's growth as the move from coordination to chartered program leadership, and ties his development directly to resolving the operating-model ambiguity at the center of P1 and REC-001.

Training Plan — Tomasz Kowalski · Focus & Years 1–2Mutechs · June 2026

Application Security Engineer · Product Security · Permanent Employee

Development Focus

Tomasz already splits his time evenly between Application Security and DevSecOps — an even balance that points clearly at his growth direction. He is the team's emerging pipeline-security specialist: security gates in CI/CD, guardrails as code, and supply-chain integrity. His growth thesis is to own the DevSecOps surface of the SDLC, becoming the engineer who makes security gates automated, fast, and trusted by developers rather than a tax on them.

The path forward concentrates his development on pipeline depth, where the team's secure-by-design ambitions either succeed or stall. As gates are chartered under P3, Tomasz is the engineer who builds the automation behind them.

Year 1
Own the CI/CD security-gate implementation across pipelines — SAST/DAST integration, policy-as-code (OPA), and dependency scanning — partnering with Raj on the core squad. Ties to P3 (Embed Security in the SDLC).
Build supply-chain security depth: SBOM generation, artifact signing, and pipeline-integrity controls.
Strengthen Terraform and guardrails-as-code fluency to participate in pipeline policy that touches cloud configuration.
Year 2
Grow into a Senior Application Security Engineer scope, owning the DevSecOps tooling roadmap for Product Security and setting gate standards other squads inherit.
Cross-train with Security Engineering on vulnerability KPIs so pipeline findings feed a consolidated remediation view (connects to REC-009).
Training Plan — Tomasz Kowalski · Year 3 & ContinuityMutechs · June 2026

Application Security Engineer · Product Security · Permanent Employee

Year 3
Establish himself as the team's DevSecOps technical lead, and a credible second voice on platform secure-design alongside Raj.
Cross-Training & Knowledge Continuity

Tomasz is developing into the team's pipeline-security specialist, which creates concentration risk if that knowledge lives only with him. To build succession depth:

Document gate configurations, policy-as-code rules, and pipeline runbooks in Confluence as the team's shared reference.
Pair with Raj as a mutual backup on CI/CD security so neither engineer is the single owner of the pipeline surface.
Bring Devin Cole into pipeline-gate operations during the contractor knowledge-transfer window so coverage is not tied to a single permanent engineer.
Notable Quote
"Developers don't fight a gate that's fast and tells them exactly what to fix. My job is to make the secure path the easy path."

Context: Tomasz frames pipeline security as developer enablement, which is precisely the mindset P3 needs — gates that scale because engineers accept them, not because they are forced.

Training Plan — Victor Moreau · Focus & Years 1–2Mutechs · June 2026

Manager, Security Engineering · Security Engineering · Permanent Employee

Development Focus

Victor leads the team that carries vulnerability-management operations and the security tooling that automates them. His time today splits across program management, security tooling and automation, and hands-on vulnerability management — a working manager who still builds. His growth thesis is a move from team lead toward platform-and-automation leadership: an operator who turns the organization's repetitive security work into engineered, self-running platforms and who sets the engineering standard the rest of the security teams adopt.

The defining test in front of him is structural. Vulnerability management is spread across his team, Cloud & Platform Security, and Product Security with no single owner holding cross-team authority (RISK-008). Victor is the named manager over that seam, and his development is inseparable from closing it. The leadership move is to charter clear program ownership rather than to absorb the work himself.

Year 1
Stand up the chartered vulnerability-management program under his team: name Sarah Whitfield as the program owner and give her the decision rights and consolidated SLAs, aging, and KPIs the role needs (REC-009). Ties to P1 (Operating Model).
Represent Security Engineering in the governance cadence forming under P1, translating remediation metrics into the business scorecard — audit readiness and platform uptime.
Build a single automation backlog across the team so tooling work is prioritized as a product, not handled ad hoc, and is no longer concentrated in one contractor.
Year 2
Grow the team's tooling-and-automation function into a shared platform other security teams build on — detection, cloud, and GRC workflows — positioning Security Engineering as the automation authority across the organization. Ties to P3 (Embed Security in the SDLC).
Develop people-leadership depth: documented career plans for every teammate and succession mapping for each single-owner capability on the team (REC-015).
Reduce single-vendor dependence by planning the conversion of contractor tooling capacity to permanent ownership (REC-017).
Training Plan — Victor Moreau · Year 3 & ContinuityMutechs · June 2026

Manager, Security Engineering · Security Engineering · Permanent Employee

Year 3
Step into a broader platform-engineering leadership remit spanning vulnerability management, security automation, and shared tooling for the whole security organization.
Grow an emerging team lead so his own role carries a documented backup, closing the key-person loop at the management layer.
Cross-Training & Knowledge Continuity

Victor's continuity obligation runs in two directions. Downward, he must make sure the program and tooling knowledge on his team lives in more than one head:

Charter Sarah as the documented program owner and Nina Castellanos as her backup, so vulnerability management survives any single absence.
Require the automation Kofi Mensah builds to be documented and owned by permanent staff, not held in a contractor's working knowledge.

Upward, his own role carries leadership-table context and the relationships that make cross-team remediation work. Identifying and growing a deputy lead is the succession-depth move that makes the team resilient at the management layer.

Notable Quote
"Coverage was never our problem — accountability was. My job is to give vuln management one owner with real authority, not to quietly carry it myself."

Context: Victor frames the vulnerability-management seam as an ownership question rather than a capacity one, which is exactly the reframe that turns a structural gap into a chartered program.

Training Plan — Wei Zhang · Focus & Years 1–2Mutechs · June 2026

Staff Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Development Focus

Wei is the deepest cloud-security engineer on the team and the single owner of every infrastructure-as-code guardrail and the CSPM stack governing the multi-tenant estate. That depth is an asset and a concentration: the capability sits with one holder and no documented backup (RISK-002). His growth thesis is to convert personal mastery into a durable, shared platform — to become the architect of how Mutechs does cloud guardrails, not the only person who can run them.

The career trap for a staff engineer in Wei's position is that indispensability blocks advancement: he cannot take on bigger architecture work while he is the sole pager for the existing stack. The path forward pairs technical growth with deliberate knowledge transfer, so that handing off operational ownership is the thing that frees him to grow.

Year 1
Lead the documentation-as-code effort under REC-003: codify guardrail policy (OPA, Terraform) and CSPM (Wiz) configuration so the stack is reproducible from the repository. Ties to P4 (Cloud & Platform Guardrails).
Author runbooks for guardrail enforcement, posture-finding triage, and break-glass changes, and pressure-test them by having a backup run a real task from the doc alone.
Begin formal mentoring of a named backup (Priscilla Adeyemi) through paired work on live posture remediation.
Year 2
Grow into cloud security architecture: design the guardrail model that will absorb the acquired Lumify cloud organization (REC-006), rather than maintaining two divergent estates.
Mature detection-relevant cloud telemetry in partnership with Detection & Response, supporting cloud-native coverage (P2, REC-014).
Pursue staff-level external validation (advanced cloud-security or Kubernetes-security certification) to anchor the architect trajectory.
Training Plan — Wei Zhang · Year 3 & ContinuityMutechs · June 2026

Staff Cloud Security Engineer · Cloud & Platform Security · Permanent Employee

Year 3
Operate as the team's principal cloud-security architect: setting standards, reviewing designs, and owning the guardrail vision while day-to-day enforcement runs through a shared, documented model.
Mentor more than one engineer so the capability has genuine bench depth, not a single named successor.
Cross-Training & Knowledge Continuity

This is the core of Wei's plan, not an afterthought. The capability he holds is the highest-severity single point of failure in Cloud & Platform Security, and the continuity work is framed as succession depth that advances his career, not as insurance against him:

Documentation-as-code: every guardrail policy and CSPM rule lives in version control with readable intent, owned by the team, reviewed each quarter. The repository, not Wei's memory, is the source of truth.
Named backup: Priscilla Adeyemi is designated the documented second owner, with scheduled shadowing on guardrail changes and posture remediation until she can run the stack unaided.
Runbooks: tested, scenario-based runbooks for enforcement, exception handling, and incident-time changes, validated by having the backup execute them solo.
Rotation: Wei and Priscilla alternate guardrail on-call so the second owner stays current and Wei can step fully away without the function degrading.

REC-013 names this capability explicitly as a single-owner state to be backed up; REC-017 (convert contractor spend to senior permanent hires) would add a second permanent engineer to make the bench durable beyond one backup.

Notable Quote
"Right now the guardrails are basically my brain in production. If it's all in code and someone else can run it, I finally get to build the next thing instead of babysitting this one."

Context: Wei sees knowledge transfer as the unlock for his own advancement rather than a loss of status, which is the mindset that makes documentation-as-code and a named backup actually stick.

CyberSN
Thank you
CyberSN · Confidential — for Mutechs CISO use