
Severity is the impact if the risk is realized; likelihood is the probability on the current trajectory; priority combines the two with urgency.
Every risk maps to at least one recommendation in the Workforce Intelligence report — the table and the recommendations are two views of the same plan, and each risk retires as its mapped actions land.
By category: structural 5 · capability 3 · operational 3 · strategic 3 · vendor 1 · By urgency: immediate 3 · near-term 9 · medium-term 3.
| ID | Risk | Category | Severity | Likelihood | Priority | REC # |
|---|---|---|---|---|---|---|
| RISK-001 | Detection engineering depends on a single teammate | Structural | Critical | High | Critical | 002, 013, 014, 017 |
| RISK-002 | Cloud guardrails and posture rest on one staff engineer | Structural | Critical | High | Critical | 003, 013, 017 |
| RISK-003 | Incident command authority is informal | Structural | High | High | High | 004 |
| RISK-004 | Identity delivery depends on a single vendor | Vendor | High | High | High | 005, 017 |
| RISK-005 | Acquired Lumify stack remains unintegrated | Strategic | High | High | High | 006 |
| RISK-006 | Product security has influence without authority | Structural | High | High | High | 001, 007 |
| RISK-007 | Compliance scale rests on a single overloaded owner | Capability | High | High | High | 008, 013 |
| RISK-008 | Vulnerability management ownership is split with no program authority | Structural | Medium | High | High | 001, 009 |
| ID | Risk | Category | Severity | Likelihood | Priority | REC # |
|---|---|---|---|---|---|---|
| RISK-009 | Tier-1 monitoring is fully outsourced with an immature SLA | Operational | High | Medium | High | 010, 017 |
| RISK-010 | Operating model ambiguity from rapid growth | Strategic | High | High | High | 001, 016 |
| RISK-011 | Third-party risk program is nascent and single-staffed | Capability | Medium | High | Medium | 012 |
| RISK-012 | Customer-questionnaire turnaround is a deal bottleneck | Operational | Medium | High | Medium | 011 |
| RISK-013 | Thin GRC bench limits audit scale | Capability | Medium | Medium | Medium | 008, 016 |
| RISK-014 | Detection coverage for the multi-tenant cloud is limited | Operational | Medium | High | Medium | 002, 014 |
| RISK-015 | Strong team culture is unprotected by career structure | Strategic | Medium | Medium | Medium | 015 |
| Severity \ Likelihood | High | Medium | Low |
|---|---|---|---|
| Critical | R-001, R-002 | — | — |
| High | R-003, R-004, R-005, R-006, R-007, R-010 | R-009 | — |
| Medium | R-008, R-011, R-012, R-014 | R-013, R-015 | — |
| Low | — | — | — |
Cells show risk ids (R-001 … R-015); full titles are in the table grid and the risk-detail cards that follow. The upper-left concentration is where the Now-horizon recommendations point.
The risks are not independent. Four clusters compound — and each cluster already has its controls sequenced in the recommendations.
All 15 risks — evidence, consequence, and mapped actions
Detection & Response engineers virtually all of its platform detections through one Senior Detection Engineer. Detection engineering accounts for roughly 12% of team time and is held by a single teammate, while tier-1 monitoring is fully outsourced to the Northbeam MDR vendor.
All infrastructure-as-code guardrails and cloud security posture management are owned by a single Staff Cloud Security Engineer with no documented backup. This capability sits at roughly 6% of Cloud & Platform Security team time with one holder, despite governing the entire multi-tenant estate.
Incident response carries no formalized command structure. The Detection & Response manager holds incident command informally, and on-call depth is thin, with incident-response capability concentrated in two teammates.
Identity & Access has one permanent teammate (the manager); all engineering is delivered by three Keystone Identity Partners contractors, and the de facto identity architect is a contractor. The IAM Architect position is vacant.
Eighteen months after the Lumify acquisition, its separate cloud organization and identity directory remain unmerged and are maintained informally by one ex-Lumify engineer inside Cloud & Platform Security. The Lumify estate sits outside core guardrails and SSO.
Embedded product-security engineers report into Engineering with only a dotted line to the central security organization. The Director of Product Security can advise squads, and cannot require secure-design outcomes, creating a seam between central security and product delivery.
The SOC 2 and ISO 27001 audit calendar and the customer-security-questionnaire pipeline are held by a single GRC director against a thin analyst bench. Compliance and governance capability is concentrated, with no deputy to absorb audit scale.
Vulnerability-management work is spread across Security Engineering, Cloud & Platform Security, and Product Security with no single program owner holding cross-team authority. Coverage exists; accountability for org-wide remediation does not.
Half of Detection & Response is Northbeam MDR contractors covering tier-1, and the vendor SLA and tier-1/tier-2 hand-off are not yet matured. Internal SOC depth is limited beyond the detection engineer and IR analysts.
The security organization was assembled reactively during hypergrowth. Ownership overlaps between product and central security, there is no RACI for shared work, and no governance cadence ties the teams to the roadmap.
Third-party risk is a single-analyst effort even as Mutechs depends on three security vendors and integrates acquired companies. There is no vendor tiering, workflow, or mandatory pre-integration security review.
Enterprise security questionnaires and trust-package responses are handled by a single Customer Trust analyst. As deal volume grows, turnaround time lengthens and slows the sales cycle.
Beyond the single owner, the GRC bench has limited depth to absorb the added scope of ISO 27001 alongside SOC 2 and growing customer commitments, with manual evidence collection.
Cloud-native detection coverage is bounded by what a single detection engineer can build. Detection-as-code is early, and coverage mapping across the multi-tenant platform is incomplete.
Team culture is the organization's retention asset (survey 4.4), and it sits on top of role overload, ambiguous ownership, and thin formal career planning (about 19% of surveyed staff have a documented plan). The asset is real and unmanaged.
This table is a living artifact, not a point-in-time list. Review it quarterly: re-score likelihood as roles fill and controls land, retire risks whose mapped recommendations complete, and add new entries as the roadmap and the workforce evolve.
Paired with the workforce-data refresh cadence, the table turns this assessment into continuous workforce intelligence — gaps stay tracked, owned, and updated as the roadmap advances.
