The images in this article were generated with artificial intelligence. How we publish
Insurers and regulators are turning their eyes to what we might call the "identity position" of companies: how they manage passwords, privileged accounts and authentication mechanisms. It is not a surprise: according to the IBM Threat Intelligence Index 2025, one in three intrusions goes through committed employee accounts. This has made identity management a key factor in assessing cyber risk and setting insurance premiums.
The economic context does not help to relax. The overall average cost of a data leak remains very high - IBM places that figure at around $4.4 million by 2025 - and many organizations are looking for policies to transfer part of that risk ( IBM Cost of a Data Break Report). In countries such as the United Kingdom, access to coverage has increased in recent years, but at the same time insurance companies tighten the requirements: where basic controls were enough to show first, evidence of continuous and effective practices is now called for ( Cyber Security Breaches Survey 2025).

Why does identity weigh so much on policy subscription? The answer is simple and technical at the same time: most effective attacks begin by obtaining valid credentials. From that point of support an attacker can climb privileges, move laterally and, if the defenses are weak, maintain persistence. For an insurer, good identity governance reduces the likelihood that a single initial access will trigger a catastrophe that will end up in a millionaire claim.
When evaluators review an organization, they pay attention to practical and measurable issues. Password hygiene remains relevant because, despite the rise of the MFA and the initiatives without a password, many authentication still depends on credentials. The problem appears when there is reuse of passwords in critical accounts, old protocols that allow for the theft of credentials more easily, inactive accounts that retain access or service accounts with passwords that never expire. The shared use of administrative credentials is also a matter of concern: it makes traceability difficult and multiplies the impact of a stolen credential.
Another critical area is the management of privileges. High-permit accounts, whether they are domain administrators, cloud administrators or service accounts with privileges, are often overassigned and outside central control. If an attacker can turn a normal account into a low-moving administrator, the risk is triggered and the premiums will reflect it. This is why subscribers review the composition of administrative groups, the existence of overlapping privileges and the registration and monitoring coverage in these accounts. In environments with Active Directory and cloud services, tools that detect inactive accounts or overassigned roles help to demonstrate that the organization controls its privilege perimeter; Microsoft for example offers guides to modernise authentication and reduce the dependence on inherited protocols ( Microsoft: disable legacy authentication).
The effective coverage and application of MFA (multifactor authentication) has become a recurring requirement. It is not enough to declare that MFA has been deployed: insurance companies seek application evidence consisting of remote access, e-mail, administrators and critical routes. Exceptions, non-interactive accounts or old protocols that dodge the second factor create shortcuts that attackers exploit after obtaining initial credentials. At this point the American technical orientation is instructive: the NIST SP 800-63B it contains recommendations on modern authentication that many risk assessments use as a reference.
Improving the identity position is not a task of immediate effects or of "activating a switch"; it is a process of maturity. Good news: insurers often value documented progress both or more than a perfect configuration from the first day. Start measuring, auditioning and correcting regularly transmits intention and reduces the probability of surprises. Audit tools for Active Directory and cloud platforms allow to quantify password exposure, identify forgotten privileged accounts and demonstrate that robust authentication policies are applied.
Remove weak passwords and share credentials It's an operational priority. Adopting minimum standards, avoiding re-use in critical accounts and forcing reasonable rotations reduces the surface that attackers can use after a leak. At the same time, documenting and auditing it creates the evidence that insurers seek.
Apply MFA at all critical points should no longer be a recommendation and become a standard: remote access, cloud management, corporate mail and any exposed interface that allows data control or exfiltration. It is not just a question of deploying MFA, but of ensuring that it covers all relevant roads and that exceptions are justified and controlled.
Reducing permanent privileged access by just-in-time models or temporary accesses limits the window in which a compromised credential can hurt. Less accounts always active with maximum permits means less systemic risk and therefore arguments for negotiating more favourable insurance conditions.

Review and certify permissions regularly is the most direct way to find orphan accounts, obsolete rights or members of administrative groups that should not have them. Routine access audits, with evidence of corrections, are currency in underwriting processes.
To demonstrate this work to insurers and auditors it is appropriate to rely on standards and tools that generate metrics and traces. Agencies and projects such as the OWASP have documented how credentials-based attacks occur on a large scale, and guides such as NIST or recommendations from manufacturers help to design a coherent strategy. There are also commercial solutions that provide visibility on password exposure in Active Directory and help prioritize remediations, for example, Specops Password Auditor is one of the tools used in Windows environments for that purpose.
At the end of the day, the message that insurance markets are sending is clear: identity management is no longer a purely operational matter to become a fundamental criterion of financial risk. Organizations that want better insurance conditions should combine technical controls with continuous review processes and the ability to demonstrate this progress. It is not a fashion: it is an adaptation to how adversaries attack today and how risk is valued by those who take financial responsibility when something goes wrong.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...