IT and cyber risk assessment, UAE

A risk register with forty entries and no owner is a document. A register with eight risks and a name against each is a decision.

A risk assessment answers four questions: what could go wrong, how likely is it, what would it cost, and what are we going to do. Everything else is presentation. We work to a recognised method, quantify where quantification is honest, and hand over a register the business can actually maintain.

IT and cyber risk assessment for UAE organisations
  • Four questionsWhat, how likely, how bad, what now
  • Named ownersEvery risk, and every treatment
  • Recognised methodAligned to published guidance
  • MaintainableA register that survives the engagement
How we assess

Seven things that determine whether a risk assessment changes anything.

Risk assessment is a well-established discipline with published guidance behind it. NIST Special Publication 800-30 revision 1, titled Guide for Conducting Risk Assessments and published in September 2012, remains one of the clearest statements of the method. The failures are almost never methodological.

We start from what the business does, not from the technology

A risk assessment that begins with an asset list produces a list of technical concerns. One that begins with what the organisation does, what would stop it doing that, and what the consequence would be, produces risks a board recognises. The technology enters at the second step, as the thing that fails, not as the subject.

We keep the register short enough to be worked

The most common failure is a register with dozens of entries, none of which anybody is accountable for. A register that lists everything ranks nothing. Consolidating to the risks that genuinely warrant a decision, with the rest recorded as observations, is what makes the difference between a document reviewed annually and one that drives work.

Every risk gets an owner who is not the IT manager

A risk owned by IT is a technical issue. A risk owned by the function that would suffer the consequence is a business risk with a budget holder attached. That reassignment is frequently uncomfortable and it is the single change that most improves whether treatments actually get funded and completed.

We quantify where quantification is honest

Some risks can be expressed in money: downtime cost per hour, regulatory exposure, contractual penalty, recovery cost. Others genuinely cannot, and inventing a number for them damages the credibility of the ones that can. Being explicit about which is which is more persuasive than a uniformly quantified register that nobody believes.

Treatments map to a real control catalogue

A treatment described as improve access management is not a treatment. Mapping each treatment to specific controls, using a prescriptive catalogue such as the CIS Critical Security Controls at version 8.1, converts the register into a work plan. It also lets you show which risks a piece of security spending actually reduces.

Accepted risks are recorded as decisions, with a name and a date

Risk acceptance is a legitimate treatment and it is frequently the right one. What makes it defensible is that somebody with the authority to accept it did so knowingly, in writing, with a review date. An accepted risk with no name attached is not an acceptance, it is an omission that will be described as one after an incident.

The register is designed to be maintained by you

An assessment that produces a register only we can update has failed. Format, terminology and scoring are agreed so that your own people can add a risk when something changes, and so the next review is an update rather than a repeat engagement. That is the difference between an assessment and a risk management function.

The failure mode

Most risk registers fail at ownership, not at methodology.

The method is well documented and rarely the problem. What goes wrong is who is named against each entry.

  • A risk owned by the IT manager is a technical issue competing with every other technical issue for the same budget and the same attention. It will be reviewed, agreed to be important, and not funded.
  • The same risk owned by the finance director, the operations director or whoever would carry the consequence is a business risk with an owner who can escalate it. Nothing about the risk changed. The reassignment is what changes the outcome.
  • The same applies to acceptance. An accepted risk needs a named person with the authority to accept it, a date, and a review point. Without those three it is not an acceptance and it will not be treated as one afterwards.
  • This is uncomfortable to do and it is the reason we do it during the assessment rather than leaving it as a recommendation. Every risk leaves the workshop with a name against it, agreed in the room.
Ask us to run the ownership session
How we approach it

Four things that turn an assessment into a risk management function.

The method is not the hard part. Published guidance such as NIST Special Publication 800-30, Guide for Conducting Risk Assessments, has been available since September 2012. What makes an assessment work is entirely in the execution.

We assign business owners in the room

Every risk leaves the workshop with a named owner who would carry the consequence, agreed in front of the people who need to agree it. Doing this as a recommendation afterwards produces a register where IT owns everything, which is the most reliable predictor that nothing will be funded.

We consolidate ruthlessly

A register that lists everything ranks nothing. We consolidate to the risks that genuinely warrant a decision at leadership level, and record the rest as observations feeding the technical work plan. A short register gets read. A comprehensive one gets filed, and the difference is not the quality of the analysis.

We map treatments to a prescriptive control catalogue

The CIS Critical Security Controls at version 8.1 give eighteen named controls in a prioritised order. Mapping each treatment to specific controls converts a risk register into a work plan, lets you show which risks a piece of spending reduces, and removes the gap between the risk document and the security programme.

We are explicit about what we cannot quantify

Downtime cost per hour, recovery cost and contractual exposure can often be estimated with the business. Reputational damage generally cannot, and inventing a figure for it makes a reader distrust the numbers that were real. Saying which is which is more persuasive than a uniformly quantified register nobody believes.

Where this fits

Six UAE situations where a risk assessment is the right starting point.

The trigger is usually external: a regulator, an insurer, a customer, a board question or an acquisition. Occasionally it is an incident, which is the most expensive way to start.

A regulated firm asked to demonstrate a risk-based approach

UAE regulatory frameworks commonly require controls proportionate to risk without prescribing which controls. That obligation is unanswerable without a documented risk position. An assessment with named owners, recorded acceptances and treatments mapped to specific controls is what turns a proportionality requirement into an evidenced position.

An organisation completing a cyber insurance application

Insurer questionnaires increasingly ask what your material risks are and what you are doing about them, not only whether specific controls exist. A current register with owners and treatments is a materially better answer than a control checklist, and it usually improves the conversation about what is and is not covered.

A board that has started asking whether the organisation is safe

That question cannot be answered with a control list. A short register in business language, with quantification where honest, an owner against each entry and a clear statement of what has been accepted, is the artefact that answers it and that a board can act on. It also tends to make the next budget conversation shorter.

An operator whose real exposure is availability rather than data

For plants, logistics and production businesses the dominant risk is usually not disclosure, it is stopping. Framing the assessment around what halts operations, for how long, and at what hourly cost produces a register that operations recognises, and treatments that land on recovery and monitoring rather than on data controls.

An organisation before or after an acquisition

Acquisitions bring an estate nobody has assessed, contracts nobody has read and controls nobody has verified. A risk assessment scoped to the acquired entity, using the same method and format as the parent, is what makes the two comparable and what identifies the integration work that genuinely cannot wait.

An organisation with a register nobody has updated in three years

The most common situation we are called into. The right response is usually to update rather than replace, keeping whatever structure people already recognise, correcting the ownership, consolidating the length and mapping treatments to controls. A rebuilt register that nobody recognises has the same fate as the one it replaced.

Three positions

How UAE organisations understand their IT risk.

The middle column is the most common. A register exists because somebody asked for one, it is comprehensive, and no decision has ever been taken because of it.
Risks expressed in business terms
A maintained risk registerYes
A register produced for an auditPartly
No formal risk viewNo
Owner named per risk
A maintained risk registerYes
A register produced for an auditIT, for all of them
No formal risk viewNo
Owner able to fund treatment
A maintained risk registerYes
A register produced for an auditNo
No formal risk viewNot applicable
Quantified where honest
A maintained risk registerYes
A register produced for an auditUniformly or not at all
No formal risk viewNo
Treatments map to specific controls
A maintained risk registerYes
A register produced for an auditNo
No formal risk viewNo
Acceptance recorded as a decision
A maintained risk registerYes
A register produced for an auditImplicitly
No formal risk viewNo
Updated between reviews
A maintained risk registerYes
A register produced for an auditNo
No formal risk viewNot applicable
Used to prioritise spending
A maintained risk registerYes
A register produced for an auditNo
No formal risk viewNo
Survives a regulator question
A maintained risk registerYes
A register produced for an auditPartly
No formal risk viewNo
Maintained by whom
A maintained risk registerYou
A register produced for an auditNobody
No formal risk viewNot applicable
What we assess

Nine risk areas, and the question each one asks.

The areas below are how we structure an assessment. The treatments map to a prescriptive control catalogue, which for most UAE organisations means the CIS Critical Security Controls at version 8.1.
Risk areaThe question it asksWhere treatment usually lands
Availability of critical servicesWhat stops the business operating, and for how longData recovery, network infrastructure, incident response
Confidentiality of sensitive dataWhat data would hurt most if disclosed, and who can reach itData protection, account management, access control
Integrity of records and transactionsWhat would happen if a record were changed and nobody noticedAudit log management, application security
Identity and privileged accessWho could act as somebody else, and would you knowAccount management, access control, audit logging
Third parties and suppliersWho has access to your systems and data, and under what termsService provider management
Endpoints and the estateWhat exists, what is unpatched, and what is unmanagedEnterprise and software asset inventory, vulnerability management
People and processWhat could be done in error, and what would prevent itSecurity awareness and skills training
Regulatory and contractual exposureWhat have you promised, and to whomVaries by obligation, mapped per requirement
Detection and response capabilityWould you know, and what would you doNetwork monitoring, incident response management
How an engagement runs

Five steps, and the workshop is where the value is created.

Typically four to eight weeks. The analysis can be done from documents and interviews. The ownership decisions can only be made with the right people in the room, which is what sets the pace.
  1. 1

    Establish scope, context and what is driving it

    Which entities and locations, whether this is cyber risk or IT risk broadly, whether third parties are included, and what obligation or question prompted the assessment. That last one determines what has to be evidenced and in what form, and it is worth being explicit about rather than assuming.

  2. 2

    Understand what the business does and what would stop it

    Before any technology is discussed. What the organisation actually does, which processes are critical, what the tolerance for interruption is, and what the consequence of disclosure or corruption would be. The technology enters at the next step as the thing that fails, which produces risks a board recognises.

  3. 3

    Identify, analyse and consolidate

    Risks identified from the business view, the technical position, the third-party picture and any recent incidents. Then analysis of likelihood and consequence, with quantification where it is honest and an explicit statement where it is not. Then consolidation, because a register that lists everything ranks nothing.

  4. 4

    Assign ownership and agree treatment in the room

    Each risk gets a business owner who would carry the consequence, agreed with the people present rather than recommended afterwards. Treatment decided as treat, transfer, accept or avoid, with accepted risks recorded as a named decision with a date and a review point. Treatments mapped to specific controls.

  5. 5

    Hand over a register you can maintain

    Format, terminology and scoring agreed so your own people can add and update entries. A process for how a new risk enters the register, when accepted risks are reviewed, and how treatments reach the budget cycle. The measure of success is that the next review is an update rather than a repeat engagement.

Straight answers

What organisations ask about risk assessments.

Before the assessment

Fifteen things that make the output usable.

The first group is scope, the second is participation, and the third is what happens afterwards, which determines whether the register is a live document or an artefact.

Scope

  • Which entities and locations?
    Groups often assess one and generalise.
  • Is this cyber risk or IT risk broadly?
    They overlap and are not the same.
  • Are third parties in scope?
    Frequently where the largest exposure sits.
  • Is there an existing register?
    Updating beats replacing.
  • What obligation is driving this?
    It shapes what must be evidenced.

Participation

  • Will business owners attend, not only IT?
    Otherwise everything gets owned by IT.
  • Is finance involved for the quantification?
    They know what downtime costs.
  • Is somebody able to accept risk present?
    Acceptance needs authority.
  • Are operations represented?
    They know what actually stops the business.
  • Who signs off the register?
    Agree before, not after.

Afterwards

  • Who maintains the register?
    It must be updatable by you.
  • How does a new risk get added?
    A process, not an email.
  • When are accepted risks reviewed?
    Acceptance needs an expiry.
  • How do treatments get funded?
    Map them to a budget cycle.
  • When is the next full review?
    Annually, or after a material change.
Next step

Open your risk register and check who owns entry number one.

Tell us about critical processes, systems, known risks and management decision owners. We will confirm the requirements and proposed scope with you.