Know what happens.
Know who owns it.
A practical look at onboarding, monthly security activities, reporting, support windows, incident escalation and accountability.
A defined path from discovery to coverage.
We agree access, roles, reporting and escalation before introducing security tooling or making changes.
Scope and permissions
Identify assets, access needs, business priorities and any in-scope vendors. No testing without written authorisation.
Measure exposure
Establish an agreed asset register, current controls, major risks and unresolved exceptions.
Set workflows
Configure only the approved tools and alerts, define contacts and agree how actions reach your IT team.
Report and improve
Begin the contracted review cadence, track findings and reconcile the plan at each reporting cycle.
What a monthly engagement can include.
The table below is a proposed delivery model, not a guaranteed service level. Exact tasks, frequency, coverage, staffing and response commitments are agreed in your statement of work.
| Activity | Essentials | Growth | Advanced |
|---|---|---|---|
| Asset and access inventory | Initial baseline + periodic changes | Baseline + change follow-up | Expanded coverage review |
| Vulnerability prioritisation | Monthly review | Monthly + exception tracking | Monthly + programme trend analysis |
| Endpoint/identity hygiene | Baseline and change exceptions | Expanded checks | Expanded checks + cloud posture |
| Client update | Monthly action summary | Monthly report + proposed quarterly call | Monthly report + roadmap review |
| Alerts and incident coordination | Business-hours review as scoped | Broader review and escalation plan | Prioritised coordination as contracted |
| 24/7 SOC/MDR | Not included | Not included | Optional and separately contracted |
Clear division of responsibilities.
Security management works best when both KITAU and the customer's IT owners know who approves, implements and verifies actions.
Identify and coordinate
Review agreed tools and assets, document evidence, prioritise risks, track follow-ups and escalate according to the contracted plan.
Approve and execute
Maintain valid access and backups, approve material changes, nominate 24-hour emergency contacts and complete remediation unless delegated in writing.
How incident escalation is defined.
A clear path matters more than vague claims of constant protection.
Signal received
Alert, customer report or assessment identifies a possible issue within the contracted service hours.
Initial triage
Review available evidence, assign initial severity and identify the appropriate decision-maker.
Customer decision
Escalate to named contacts; agree containment or specialist response only within explicit authorisation and coverage.
Record & improve
Track decisions, required fixes, residual risk and lessons learned for the next report.
This describes an intended process, not a promise that any particular alert will be detected or handled within a specified period. Incident SLAs and specialist response availability must be agreed before an engagement.
Make the next security decision with confidence.
Tell us what you need to protect. We'll propose a scope, deliverables and responsibilities before any work begins.