AI Security Planner

Demo data. Any changes do not save and are reset on refresh.

Endpoint Security Consolidation

PERT

Review the dependency network. Drag to pan, or use the scrollbars, to explore the full dependency map.

Critical pathCompleteDependencies
ES-P1-M01Planned

Name the sponsor, program owner, and consolidation decision rights

Govern and design the target endpoint program

2 person-daysCritical
ES-P1-M02Planned

Define the endpoint populations and operating systems in scope

Govern and design the target endpoint program

4 person-daysCritical
ES-P1-M03Planned

Establish a baseline endpoint and ownership inventory process

Govern and design the target endpoint program

4 person-daysCritical
ES-P1-M04Planned

Map the current endpoint tools, agents, owners, contracts, and data flows

Govern and design the target endpoint program

5 person-daysCritical
ES-P1-M05Planned

Define the required management, protection, detection, response, and reporting capabilities

Govern and design the target endpoint program

4 person-daysCritical
ES-P1-M06Planned

Record platform, remote-work, offline-device, and regulated-system constraints

Govern and design the target endpoint program

3 person-days
ES-P1-M07Planned

Approve the target platform boundary and any retained specialist tools

Govern and design the target endpoint program

3 person-daysCritical
A project acceptance milestone cannot be deleted. Add or assign a replacement acceptance milestone first.
ES-P2-M08Planned

Define migration waves and fixed sequencing criteria

Design and prove the endpoint migration

4 person-days
ES-P2-M09Planned

Define pilot success, failure, rollback, and evidence criteria

Design and prove the endpoint migration

3 person-days
ES-P2-M10Planned

Prepare the target policy, configuration, role, and exception baseline

Design and prove the endpoint migration

5 person-daysCritical
ES-P2-M11Planned

Define coexistence controls for overlapping or conflicting agents

Design and prove the endpoint migration

4 person-daysCritical
ES-P2-M12Planned

Pilot a representative endpoint group with an approved rollback path

Design and prove the endpoint migration

5 person-daysCritical
ES-P2-M13Planned

Validate control coverage, operational workflows, performance, and support readiness

Design and prove the endpoint migration

5 person-daysCritical
ES-P2-M14Planned

Resolve pilot gaps and record the production go or no-go decision

Design and prove the endpoint migration

3 person-daysCritical
A project acceptance milestone cannot be deleted. Add or assign a replacement acceptance milestone first.
ES-P3-M15Planned

Migrate production waves with bounded pause and rollback criteria

Migrate, retire, and operate endpoint controls

8 person-daysCritical
ES-P3-M16Planned

Confirm target coverage and remove legacy agents from migrated endpoints

Migrate, retire, and operate endpoint controls

5 person-daysCritical
ES-P3-M17Planned

Retire approved legacy services, data flows, access, and contracts

Migrate, retire, and operate endpoint controls

4 person-daysCritical
ES-P3-M18Planned

Transfer ownership, metrics, exceptions, and executive reporting to routine operations

Migrate, retire, and operate endpoint controls

3 person-daysCritical
A project acceptance milestone cannot be deleted. Add or assign a replacement acceptance milestone first.

Critical path

15 remaining · Name the sponsor, program owner, and consolidation decision rights · Next · October 2, 2026

Dependencies

No handoffs need review

Next handoff

Name the sponsor, program owner, and consolidation decision rights · Executive sponsor · September 7, 2026

Recommendations

Recommendations requiring attention
Actions
No active recommendations for this view.
  1. No active recommendations for this view.