Team Organization — Feature Teams & Responsibilities¶

This page details what each Feature Team delivers, how to engage them, and how the overall organization maximizes user outcomes.

At a glance¶

Feature Team	Primary mission	Typical user needs it addresses	Key deliverables
FT Operations	Operate and sustain Illumio platform & protection in RUN	incidents, upgrades, agent lifecycle, sustainability, audits/DR	runbooks, standard changes, monitoring, evidence packs
FT Onboarding	Build protection for applications (flows → rules → first enforcement)	onboarding, policy build, peer qualification, workshops	cartography, validated rule set, first change support
FT Tooling	Scale delivery through automation (DevOps)	reduce manual effort, QC/drift, faster & safer delivery	CMDB sync, scripts, health checks, QC reports
FT Microcosmos	Deliver the Microcosmos portal & reporting enablement (DevOps product)	visibility, reporting, dashboards, user enablement	portal features, controlled releases, compliance fixes

FT Operations (Build & Run / MCO)¶

Mission¶

Ensure the microsegmentation service is stable, sustainable and audit-ready in production.

Core responsibilities¶

Agent installation standardization (Puppet-based approach), coordination with infra teams where needed
Troubleshoot agent issues (heartbeat, stopped agents, errors)
PCE hygiene: remove decommissioned servers and keep objects consistent
Monthly patching, vendor security patches, platform/console upgrades and agent upgrade waves
Backups, monitoring/morning checks, operational health controls
DR exercises and audit readiness (evidence, procedures, reports)
Sustainability in RUN: ensure new servers are covered; enforce mode for RUN applications
Maintain templates and documentation (Admin Guide, Runbook, DAT, New Joiner checklist, Scope form)
Change defense in local CRB; standard change template recertification

In scope / Out of scope (boundaries)¶

In scope - Platform operations, sustainability, operational controls, DR/audits - Standardized installation and recurring maintenance activities

Out of scope - Rules qualification workshops (owned by FT Onboarding) - Building new automation features (owned by FT Tooling) except operational runbook updates

How this helps users¶

Fewer incidents, faster recovery (clear operational ownership)
Safer upgrades and predictable maintenance windows
Production sustainability: protection does not “decay” over time

FT Onboarding (Security Build & Enablement)¶

Mission¶

Deliver application onboarding and protection build from flows to first enforcement, with strong stakeholder guidance.

Core responsibilities¶

Implement rules aligned with the protection strategy
Produce flow cartography and investigate unknown remote peers
Prepare and facilitate qualification workshops with application teams
Run onboarding kick-offs and maintain the onboarding playbook
Maintain and evolve Bouquets Infra and identify new global core services
Run weekly Core Services Committee and support validation
Support first protection change and planned migrations

In scope / Out of scope (boundaries)¶

In scope - Cartography, peer qualification, workshops, validated ruleset - First change support and onboarding coordination

Out of scope - PCE/agent platform operations (owned by FT Operations) - Tool/portal engineering (owned by FT Tooling / FT Microcosmos)

How this helps users¶

Faster onboarding cycle time (less back-and-forth)
Higher change success rate (rules validated before execution)
Clear guidance and predictable “next steps”

FT Tooling (DevOps)¶

Mission¶

Industrialize the service by automating repetitive work, enforcing quality controls, and improving delivery throughput.

Core responsibilities¶

Maintain and evolve CMDB sync batch (bug fixes, features, enhancements)
Maintain CI/CD and manage new versions compliant with Change Management
Maintain and evolve cartography scripts
Maintain and evolve admin scripts (daily health checks, quality controls, ruleset extraction)
Remediate corporate compliance findings through automation and engineering

In scope / Out of scope (boundaries)¶

In scope - Automation, QC/drift detection, engineering for scale

Out of scope - Direct platform operations (owned by FT Operations) - Product roadmap of the portal (owned by FT Microcosmos)

How this helps users¶

Less manual work → faster delivery
Better quality and consistency (repeatable checks)
More transparency and fewer surprises

FT Microcosmos (DevOps Product)¶

Mission¶

Build and evolve the Microcosmos portal to provide visibility, reporting and user enablement through controlled releases.

Core responsibilities¶

Maintain and evolve the portal (bug fixes, features, enhancements)
Maintain CI/CD and manage versions compliant with Change Management
Remediate compliance findings for corporate requirements

In scope / Out of scope (boundaries)¶

In scope - Portal delivery, reporting enablement, user-facing improvements

Out of scope - Rules build and onboarding workshops (FT Onboarding) - Platform operations (FT Operations)

How this helps users¶

Better self-service and reporting
Faster access to reliable information (dashboards, evidence)
Controlled releases with predictable change governance

Key Roles & how users benefit¶

Role	Focus	User benefit
Service Manager	Service quality, reporting, compliance, communication	clear service ownership and escalation
Product Owner	prioritization, roadmap, stakeholder value	predictable roadmap and prioritization transparency
Delivery Manager	execution coordination, major incidents & change orchestration	smoother delivery and fewer handover gaps
Scrum Masters (per FT)	flow efficiency, impediment removal	delivery predictability and continuous improvement

How to engage the right team (quick guide)¶

I need to onboard an application / qualify flows / build rules → FT Onboarding
I have a platform/agent incident, upgrade, or sustainability issue in RUN → FT Operations
I need automation, a QC report, or a tooling enhancement → FT Tooling
I need a portal/reporting feature or visibility improvement → FT Microcosmos