SCOPED, DOCUMENTED, ACTIONABLE

Know what happens.
Know who owns it.

A practical look at onboarding, monthly security activities, reporting, support windows, incident escalation and accountability.

Onboarding

A defined path from discovery to coverage.

We agree access, roles, reporting and escalation before introducing security tooling or making changes.

01 / DISCOVER

Scope and permissions

Identify assets, access needs, business priorities and any in-scope vendors. No testing without written authorisation.

02 / BASELINE

Measure exposure

Establish an agreed asset register, current controls, major risks and unresolved exceptions.

03 / ACTIVATE

Set workflows

Configure only the approved tools and alerts, define contacts and agree how actions reach your IT team.

04 / REVIEW

Report and improve

Begin the contracted review cadence, track findings and reconcile the plan at each reporting cycle.

Example maintenance rhythm

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.

ActivityEssentialsGrowthAdvanced
Asset and access inventoryInitial baseline + periodic changesBaseline + change follow-upExpanded coverage review
Vulnerability prioritisationMonthly reviewMonthly + exception trackingMonthly + programme trend analysis
Endpoint/identity hygieneBaseline and change exceptionsExpanded checksExpanded checks + cloud posture
Client updateMonthly action summaryMonthly report + proposed quarterly callMonthly report + roadmap review
Alerts and incident coordinationBusiness-hours review as scopedBroader review and escalation planPrioritised coordination as contracted
24/7 SOC/MDRNot includedNot includedOptional and separately contracted
Coverage is not the same as incident response. Standard starting plans do not include an always-on SOC, guaranteed response clock, remote containment rights or emergency recovery unless contracted. We confirm support windows, severity handling and escalation contacts in writing.
Working agreement

Clear division of responsibilities.

Security management works best when both KITAU and the customer's IT owners know who approves, implements and verifies actions.

KITAU / SCOPED PROVIDER

Identify and coordinate

Review agreed tools and assets, document evidence, prioritise risks, track follow-ups and escalate according to the contracted plan.

CUSTOMER / IT OWNER

Approve and execute

Maintain valid access and backups, approve material changes, nominate 24-hour emergency contacts and complete remediation unless delegated in writing.

Typical exclusions: general helpdesk and desktop support, 24/7 monitoring, emergency incident containment, forensic investigation, full disaster recovery, software licences, audit certification and major remediation projects unless separately specified.
When something is wrong

How incident escalation is defined.

A clear path matters more than vague claims of constant protection.

01

Signal received

Alert, customer report or assessment identifies a possible issue within the contracted service hours.

02

Initial triage

Review available evidence, assign initial severity and identify the appropriate decision-maker.

03

Customer decision

Escalate to named contacts; agree containment or specialist response only within explicit authorisation and coverage.

04

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.

LET'S SCOPE IT TOGETHER

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.

Request a consultation →