Back to solutions
CIO Assessment

Do you know where your IT is vulnerable?

Twenty-four questions help you assess systems, ownership and security controls. The result is a starting point, not a certification or a substitute for technical review.

Do you know where your IT is vulnerable?
Service illustration
Six assessment domains

A CIO score needs to see more than four isolated technical metrics.

The 24 answers are evaluated by domain and overall, highlighting areas needing review even with a good total.

Identity & Access

Identities, privileged access and authentication.

4 questions

Endpoint & Workplace

Devices, compliance, patching and standardized provisioning.

4 questions

Infrastructure & Network

Servers, networking, lifecycle, capacity and technical dependencies.

4 questions

Security & Recovery

Detection, backup, recovery and incident capability.

4 questions

Service Operations & SLA

Tickets, monitoring, escalation, support and measurable service quality.

4 questions

Governance & Strategy

Ownership, risk, vendors, roadmap and management control.

4 questions
1/6
24 questions · about 6–8 minutes
Domain 1 / 6

Identity & Access

Identities, privileged access and authentication.

01

How consistently is MFA enforced for users and administrators?

02

How clearly are administrative accounts separated from normal user accounts?

03

How reliably do joiner, mover and leaver processes work?

04

How controlled is the assignment, review and removal of privileged roles?

Domain 2 / 6

Endpoint & Workplace

Devices, compliance, patching and standardized provisioning.

01

How completely are clients and mobile devices centrally managed?

02

How reliably are operating systems and applications patched?

03

How consistently are endpoint security, hardening and local privileges implemented?

04

How standardized and repeatable is device provisioning?

Domain 3 / 6

Infrastructure & Network

Servers, networking, lifecycle, capacity and technical dependencies.

01

How current and reliable is your technical inventory including dependencies?

02

How consistently are lifecycle, maintenance levels and end-of-life risks managed?

03

How clearly are network zones, segmentation and access rules structured?

04

How early do you detect capacity, performance or availability bottlenecks?

Domain 4 / 6

Security & Recovery

Detection, backup, recovery and incident capability.

01

How centralized and usable are security and system logs?

02

How well does your backup architecture protect against failure, tampering and ransomware?

03

How regularly are real restore or disaster-recovery tests performed?

04

How clear are roles, escalation, evidence preservation and communication during critical incidents?

Domain 5 / 6

Service Operations & SLA

Tickets, monitoring, escalation, support and measurable service quality.

01

How completely do support requests and incidents flow through a controllable process?

02

How well does your monitoring detect real service problems rather than isolated technical metrics?

03

How transparently and reliably are SLA and response targets measured?

04

How systematically are recurring incidents investigated for root causes rather than symptoms?

Domain 6 / 6

Governance & Strategy

Ownership, risk, vendors, roadmap and management control.

01

How clearly are technical and business owners assigned to critical services?

02

How systematically are IT risks assessed, prioritized and tracked?

03

How transparent are dependencies, SLAs and risks of your key IT suppliers?

04

How reliably do you connect technical roadmap, budget and business priorities?

0–39Fragile

Critical gaps and heavy person-dependency. Establish transparency and baselines first.

40–59Reactive

Foundations exist, but too much is still manual or inconsistent.

60–74Structured

Good standards, but measurability, recovery or governance still have visible gaps.

75–89Controlled

Defensible operating model with targeted optimization areas and good control.

90–100Resilient

Responses suggest a developed operational base. Verify evidence and opportunities for efficiency and automation.

Methodology

A management indicator, not a certificate.

The overall score is calculated from your answers. Review each domain too: a good average can hide a critical gap. Use specific answers and verifiable evidence to decide next steps.

What follows in a CIO review
  • Validate results against actual systems, contracts and dependencies
  • Prioritize risks by business impact and likelihood
  • Separate quick wins, technical debt and investment items
  • Build a roadmap with owners, budget frame and review cadence
Next step

The score shows the direction. The review turns it into a plan.

Use the six domain scores to order open actions. Owners, effort and dates are established during further review.