Insurance readiness, UAE

The proposal form asks yes or no questions. Answering optimistically is how a claim gets disputed.

Cyber insurance applications ask about controls in specific terms. We help you establish what is actually true, evidence it, and close the gaps that matter, so the answers you give are ones you could defend at claim time.

Cyber insurance readiness for UAE organisations
  • 18 controlsIn the widely referenced control set
  • 153 safeguardsAcross the current control versions
  • IG1 firstEssential cyber hygiene as the starting point
  • EvidenceWhat separates an answer from an assertion
The risk in an optimistic answer

A proposal form is a statement about your organisation, made in writing, before an incident.

We are not insurance advisers, and this much is simply prudent: answer questions about your controls the way you would want to defend them afterwards.

  • The questions are usually binary and the reality usually is not. Multifactor authentication on all remote access is a yes or a no on the form, and in most estates the truthful answer is that it covers most access with several documented exceptions.
  • The gap between those two answers is invisible until something happens. At that point the exceptions become the interesting part of the conversation, and the organisation is explaining a discrepancy rather than dealing with an incident.
  • The practical remedy is to establish the true position first. Where a control is partial, either close the gap before answering or answer accurately and describe the exceptions, which is a conversation better had at application time.
  • None of this is legal or insurance advice, and it is not a substitute for your broker. It is a security assessment aligned to the questions insurers actually ask, so that what you state about your controls is something you have evidenced.
Ask us to establish your true position
What readiness involves

Eight things to establish before you complete a proposal form.

We are not brokers and we do not give insurance advice. What we do is establish, with evidence, whether the control statements you are about to make are true across your whole estate rather than in the part somebody was thinking of.

Asset inventory is the first control for a reason

Inventory and control of enterprise assets sits first in the published control set, followed by software assets. Almost every other control statement is qualified by scope, and scope means knowing what you have. Most estates cannot answer this precisely.

Account and access management get examined closely

Account management and access control management are separate controls. Questions about privileged accounts, multifactor coverage and joiner mover leaver processes are asking about both, and the honest answer is frequently mostly rather than yes.

Data recovery has to be demonstrated

Data recovery is a control in its own right, distinct from backup. The relevant question is not whether backups run but whether a restore has been performed and timed, which is a different and considerably less comfortable question.

Vulnerability management is continuous, not periodic

The published control is continuous vulnerability management. An annual scan is a point in time exercise, and describing it as continuous vulnerability management is exactly the kind of generous characterisation that becomes contentious later.

Audit log management is frequently the weak point

Audit log management is a distinct control covering collection, retention and review. Organisations that collect logs but retain them for two weeks, or never review them, are in a materially weaker position than the questionnaire answer suggests.

Service provider management is in scope

Service provider management is one of the eighteen controls. Questions about suppliers, their access to your systems, and what security is required of them contractually are asking about a control most organisations have not formalised.

Training is a control, with records

Security awareness and skills training is control fourteen. The distinction that matters is between having run training and being able to show completion records by person, which is what an evidence request actually asks for.

Start with essential cyber hygiene

IG1 is defined as the foundational set of safeguards every enterprise should apply to guard against the most common attacks, and the published guidance is that every enterprise should start there. It is also a realistic scope for a readiness exercise.

The control set

Eighteen controls, and what evidence typically looks like.

The controls are published and widely referenced. The right column is the evidence that turns a questionnaire answer into something you can produce on request.
ControlEvidence that supports the answer
Inventory and Control of Enterprise AssetsA current inventory with a stated discovery method
Inventory and Control of Software AssetsInstalled software list with an approval position
Data ProtectionClassification and encryption coverage stated
Secure Configuration of Enterprise Assets and SoftwareBaselines and drift detection
Account ManagementJoiner mover leaver records and dormant account reports
Access Control ManagementMultifactor coverage with the exception list
Continuous Vulnerability ManagementScan cadence and remediation timelines met
Audit Log ManagementSources, retention period and review evidence
Email and Web Browser ProtectionsFiltering configuration and its coverage
Malware DefensesDeployment coverage percentage across the estate
Data RecoveryA timed restore test, not a backup report
Network Infrastructure ManagementDevice inventory, configuration and firmware currency
Network Monitoring and DefenseWhat is monitored and who acts on it
Security Awareness and Skills TrainingCompletion records by person
Service Provider ManagementSupplier list with access and contractual requirements
Application Software SecurityTesting evidence for applications you build
Incident Response ManagementA plan plus evidence it has been exercised
Penetration TestingA recent report and the remediation status
How we approach it

Four things we do, and one we do not.

We are a technology firm. We assess controls and produce evidence. Your broker advises on cover, and the two activities complement each other without overlapping.

We state coverage as a proportion

Multifactor authentication on ninety four percent of accounts with a named exception list is a true statement. Yes is not, and the difference between them is exactly what surfaces when evidence is requested rather than accepted.

We test recovery rather than reporting on backups

Data recovery is a control distinct from taking backups. A timed restore of a representative system produces a figure you can state and defend, and it regularly produces a surprise that is far better found now than during an incident.

We prioritise gaps by how much they move the answer

Some gaps are expensive and change one answer. Others are cheap and change several. Sequencing by that ratio is what makes a readiness exercise fit inside the weeks available before a renewal rather than becoming a security programme.

We do not advise on insurance

We do not recommend cover, interpret policy wording, estimate premiums or act as a broker. What we provide is an evidenced assessment of your controls, which your broker and underwriter can then use for the parts that are properly theirs.

How an engagement runs

Three phases across roughly five to nine weeks.

Timed to sit before a renewal or an application, since that is when the answers have to be given and when the gaps are cheapest to close.
  1. 01
    Weeks 1 to 3

    Establish what is actually true

    Each control assessed against evidence rather than against recollection, with coverage stated as a proportion of the estate rather than as a yes. Exceptions are documented deliberately, because exceptions are what the binary questions conceal.

    • Control position assessed with evidence
    • Coverage stated as a proportion, not a yes or no
    • Exceptions documented per control
    • Evidence located and gathered in one place
  2. 02
    Weeks 4 to 7

    Close the gaps that matter before you answer

    Prioritised by which controls proposal forms concentrate on and by which gaps are cheap to close. Multifactor coverage, restore testing and log retention are frequently the three that move furthest in the shortest time.

    • Gaps prioritised by question weight and effort
    • Quick wins implemented and evidenced
    • Remaining gaps documented with a plan and dates
    • Position restated after remediation
  3. 03
    Weeks 8 to 9

    Assemble the evidence pack

    A single pack supporting each control statement, so that when a question is asked the answer comes with its evidence attached. The same pack serves customer security questionnaires, which is where much of its ongoing value sits.

    • Evidence pack assembled per control
    • Supporting documents dated and owned
    • Maintenance cadence agreed
    • Board summary of the control position
Where this comes up

Six situations that make readiness worth doing.

The trigger is usually a date. Renewals and applications come with deadlines, and control gaps do not close quickly under pressure.

A business applying for cyber cover for the first time

The proposal form is the first structured examination of the security position many organisations have faced. Establishing the true answers before writing them down is the difference between a smooth application and an awkward one.

An organisation approaching renewal

Renewal questions tend to become more specific each year, and the estate has changed since the last set of answers. Reassessing rather than copying forward last year responses is what keeps the statements accurate.

A company asked for evidence rather than answers

Evidence requests are increasingly common and they are where optimistic answers become visible. An organisation with an assembled pack responds in days, and one without spends weeks reconstructing a position it already asserted.

A group with inconsistent controls across entities

Group level answers frequently describe the best entity rather than the whole group. Assessing per entity and stating coverage as a proportion produces an answer that survives an examination of any single site.

An operation with technology outside the IT estate

Production systems, building management and specialist equipment are frequently excluded from inventories and from control coverage. They are rarely excluded from the questions, which is where a coverage percentage becomes important.

A business whose customers ask the same questions

Service provider management is a control, and your customers apply it to you. The evidence assembled for an insurance application answers a large part of a customer security questionnaire, which is where much of the ongoing value sits.

Three positions

How UAE organisations approach an insurance application.

The middle column is the most common, and it is fine right up until an evidence request or a claim, at which point the difference becomes very visible.
Control statements verified
Assessed and evidencedWith evidence
Completed from memoryFrom recollection
Delegated to whoever is freeGuessed
Coverage stated accurately
Assessed and evidencedAs a proportion
Completed from memoryAs a yes
Delegated to whoever is freeAs a yes
Exceptions known
Assessed and evidencedDocumented
Completed from memoryUnknown
Delegated to whoever is freeUnknown
Evidence producible on request
Assessed and evidencedSame day
Completed from memoryDays to weeks
Delegated to whoever is freeNo
Gaps closed before answering
Assessed and evidencedThe cheap ones
Completed from memoryNone
Delegated to whoever is freeNone
Position at an evidence request
Assessed and evidencedComfortable
Completed from memoryUncertain
Delegated to whoever is freeExposed
Reusable for customer questionnaires
Assessed and evidencedYes
Completed from memoryPartly
Delegated to whoever is freeNo
Board visibility of the real position
Assessed and evidencedYes
Completed from memoryOptimistic
Delegated to whoever is freeNone
Time required
Assessed and evidencedWeeks
Completed from memoryAn afternoon
Delegated to whoever is freeAn hour
Value beyond the application
Assessed and evidencedSubstantial
Completed from memoryLittle
Delegated to whoever is freeNone
A realistic scope

Essential cyber hygiene is the sensible target, and the published guidance says so.

There are 153 safeguards across the current control versions. Attempting all of them before a renewal is not a plan.

  • IG1 is defined as the foundational set of cyber defence safeguards that every enterprise should apply to guard against the most common attacks, and the published position is that every enterprise should start with IG1 regardless of size.
  • That is a coherent scope for a readiness exercise. It covers the controls that proposal forms concentrate on, it is achievable inside a renewal cycle, and it corresponds to the attacks that actually generate claims rather than to sophisticated targeted intrusion.
  • IG2 builds upon IG1 and IG3 comprises all the controls and safeguards. Progression beyond the first group is a decision based on risk profile and available resources, and it belongs in a security roadmap rather than in a pre renewal sprint.
  • The practical benefit of using a published control set is that the answers travel. The same evidence supports the insurance conversation, a customer security questionnaire and an internal board discussion without being rebuilt each time.
Ask us to scope an IG1 assessment
How an engagement runs

Five steps, timed to sit before the deadline.

Everything here works better with a few weeks in hand. Done the week before a renewal, it becomes documentation of gaps rather than an opportunity to close them.
  1. 1

    Scope to essential cyber hygiene

    The foundational set of safeguards every enterprise should apply against the most common attacks, which is both the published starting point and a realistic scope for the weeks available before an application or renewal deadline.

  2. 2

    Assess each control against evidence

    Asset and software inventory, data protection, secure configuration, account and access management, vulnerability management, logging, email and browser protections, malware defences, recovery, network management and monitoring, training, suppliers, application security, incident response and testing.

  3. 3

    State coverage honestly, with exceptions

    As a proportion of the estate rather than as a binary answer, with exceptions named. That is what converts a questionnaire response from an assertion into a statement you could stand behind if somebody asked to see the underlying position.

  4. 4

    Close what can be closed

    Prioritised by how many answers each gap affects and by how quickly it can be closed. Multifactor coverage, a tested restore and log retention are frequently the three that move the position furthest in the time available.

  5. 5

    Assemble the evidence and keep it current

    One pack per control, dated and owned, so an evidence request is a retrieval rather than a project. A maintenance cadence keeps it usable for the next renewal and for the customer questionnaires that arrive in between.

Straight answers

What organisations ask about insurance readiness.

Before you answer

Fifteen questions to answer honestly first.

The pattern to watch for is any answer that begins with mostly, generally or in principle. Those are the answers a form converts into an unqualified yes.

Access

  • Is MFA on all remote access?
    Including exceptions.
  • Is MFA on all privileged accounts?
    A separate question.
  • How many dormant accounts exist?
    A number, not a process.
  • Do leavers lose access same day?
    Evidenced how.
  • Who holds local administrator rights?
    And how many.

Recovery and logging

  • When did we last restore from backup?
    A date.
  • How long did it take?
    A measured figure.
  • Are backups isolated from the network?
    A common question.
  • How long are logs retained?
    Often shorter than assumed.
  • Who reviews them?
    Collection is not review.

Process and people

  • Has the incident plan been exercised?
    Not just written.
  • Do we have training completion records?
    By person.
  • Do we know our suppliers with access?
    A named control.
  • When was the last penetration test?
    And what was fixed.
  • Is patching within our stated timelines?
    Measured, not intended.
Next step

Take the last proposal form you completed and check one answer against evidence.

Tell us about the questionnaire, renewal deadline, systems in scope and evidence supporting current answers. We will confirm the requirements and proposed scope with you.