The project management wrapper around every Raksha deployment — from first handshake to steady-state operations. Six phases, zero ambiguity, complete accountability.
⚙ Companion Tool: Zero-Touch Deployment Framework →Every Raksha engagement follows this lifecycle. Each phase has clear deliverables, quality gates, and handoff criteria. No phase begins until the previous gate is cleared.
The foundation. Get stakeholder alignment, set expectations, define scope, assign resources, and establish governance before a single config line is written.
Detailed project plan, resource mapping, dependency tracking, and quality gates. This phase runs parallel with data gathering from the Forward Integration checklist.
Map every role needed across the engagement. Identify resource gaps early — finding a certified engineer 2 days before deployment is not a plan.
R = Responsible (does the work) A = Accountable (owns the outcome) C = Consulted I = Informed
| Activity | Raksha DM | Raksha Tech | Client SPOC | Client Net Admin | Client CISO | Vendor/OEM |
|---|---|---|---|---|---|---|
| Project Planning & Timeline | A/R | C | R | I | I | I |
| Forward Integration Data Gathering | A | R | R | R | C | I |
| Solution Architecture Design | I | A/R | C | C | C | C |
| Lab Configuration & Testing | I | A/R | I | I | I | C |
| Config Peer Review & QA | A | R | I | I | I | I |
| Change Request Submission | R | C | A | C | A | I |
| Hardware Racking & Cabling | I | C | A | R | I | I |
| Config Import & Cutover | A | R | C | R | I | C |
| Backward Integration (SIEM, Ticketing) | I | A/R | C | R | I | I |
| UAT / Sign-Off | R | C | A | R | A | I |
| Knowledge Transfer & Training | A | R | R | R | I | C |
| Hypercare Support | A | R | C | C | I | C |
| Project Closure & Handover | A/R | R | A | I | A | I |
Every milestone has a quality gate — a deliverable or sign-off that must be completed before moving forward. No shortcuts.
| Phase | Milestone | Quality Gate | Owner | Typical Week |
|---|---|---|---|---|
| P1 | Kickoff Complete | MOM distributed, action items logged, recurring meetings scheduled | Delivery Manager | Week 0 |
| P2 | Data Collection Complete | GATE All Forward Integration data received and validated | Tech Lead + Client SPOC | Week 1-2 |
| P2 | Architecture Sign-Off | GATE Solution design document approved by Client CISO/CTO | Tech Lead | Week 2 |
| P3 | Lab Config Complete | All policies, rules, integrations built and documented in lab | Impl. Engineer | Week 3-5 |
| P3 | Config Peer Review Passed | GATE Independent review completed, all findings resolved | QA / Architect | Week 5-6 |
| P3 | Golden Config Exported | Config + firmware + certs + runbook packaged in deployment kit | Impl. Engineer | Week 6 |
| P3 | Change Request Approved | GATE CAB approval for production deployment with rollback plan | DM + Client SPOC | Week 7 |
| P4 | Hardware Racked & Powered | Physical installation verified, management access confirmed | Client Net Admin | Week 8 |
| P4 | Config Imported & Verified | Golden config loaded, basic connectivity tests pass | Impl. Engineer | Week 8 |
| P4 | Production Cutover | GATE Live traffic flowing, no critical issues for 4 hours | Tech Lead | Week 8-9 |
| P4 | Backward Integrations Live | SIEM logs flowing, ticketing connected, monitoring active | Impl. Engineer | Week 9 |
| P5 | UAT Sign-Off | GATE Client confirms all scope items functional, acceptance document signed | Client CISO + DM | Week 10 |
| P5 | Knowledge Transfer Complete | Training sessions delivered, runbook handed over, L1/L2 team certified | Tech Lead | Week 10-11 |
| P5 | 30-Day Hypercare Ends | GATE No open P1/P2 issues, performance baselines stable, client self-sufficient | DM + Support Eng | Week 12 |
| P6 | Project Closure | Closure report, lessons learned, warranty/AMC handover, project archived | Delivery Manager | Week 13 |
This is where the Deployment Framework takes over. The technical playbook drives the work — this tool tracks the project governance around it.
The detailed checklists for data gathering, lab configuration, config export/import, and forward/backward integrations live in the Deployment Framework. During these phases, the Engagement Lifecycle Manager tracks:
This review happens 2-3 days before scheduled cutover. All items must be green. If any item is red, delay the cutover — it's always cheaper to reschedule than to recover from a failed deployment.
The engagement doesn't end at go-live — it ends when the client is self-sufficient and the investment is delivering measurable value.
Risks that appear in nearly every cybersecurity deployment. Start with these, then add project-specific risks during kickoff and throughout the engagement.
Structured communication eliminates surprises. Every stakeholder knows what to expect, when, and from whom.
| Trigger | Timeline | Raksha Escalation | Client Escalation |
|---|---|---|---|
| Blocker unresolved > 24hrs | Day 1 | Delivery Manager | Client SPOC |
| Blocker unresolved > 48hrs | Day 2 | Raksha Practice Head | Client IT Head / CTO |
| Critical risk materialises | Immediate | Raksha Account Director | Client CISO |
| Milestone delayed > 1 week | At 1-week mark | Raksha Practice Head | Client IT Head |
| Go-live failure / rollback triggered | Immediate | Raksha CTO | Client CISO + CTO |
| Client satisfaction issue | At discovery | Raksha Account Director | N/A (Raksha-initiated) |
A consistent format builds trust. Every weekly report follows this structure — no surprises, no missing information.
🟢 On Track | 🟡 At Risk | 🔴 Delayed [Select one and explain in 1-2 sentences]
[List 3-5 items completed with brief description]
[List 3-5 items planned with owners]
[List any new risks, open issues, or blockers with severity and owner]
[Items pending from client with due dates — this is where gentle pressure lives]
[Decisions required from client stakeholders — be specific about who needs to decide what by when]
Raksha Technologies — Cybersecurity Procurement Advisory Platform
Engagement Lifecycle Manager v1.0 | Companion to Zero-Touch Deployment Framework