Insider threat
A risk from someone with legitimate access, whether malicious, negligent or compromised. Because access is already granted, behaviour is what reveals misuse.
Reading Time:
An insider threat is a risk that comes from someone with legitimate access to an organisation’s systems and data. Because the access is already granted, the person does not need to break anything. The question is whether what they do is normal.
Employees, contractors, suppliers, partners and anyone with an account. Administrators and other privileged users carry the most risk, because their access reaches the furthest.
Theft or leakage of data, fraud, sabotage of systems, disruption of services and regulatory consequences. The impact depends on the access the person holds, which is why it is closely tied to the blast radius of their identity.
Everything an insider does is done with valid credentials, from a trusted device, using permissions granted to them. Nothing is broken and nothing is malicious in itself. Only the pattern, in context, reveals that something is wrong.
No single sign proves misuse. The combination matters.
Access controls decide what a person is allowed to do. An insider acts within that permission. A rule cannot tell a legitimate administrator from someone abusing the same rights, which needs visibility into behaviour.
A sales manager who has resigned starts exporting customer lists from the CRM at night. Their permissions allow it, so nothing is blocked. Only the change in volume and timing, compared with their normal use, stands out.
An external attacker has to obtain access first. An insider already has it. A compromised insider blurs the line, because an outsider is using an insider’s account.
People who leave or change role often keep access longer than they should, and dormant accounts that still work are easy to misuse. Prompt, complete removal of access is one of the simplest ways to reduce insider risk.
Monitoring colleagues involves personal data, so it must be proportionate, transparent and designed with data protection in mind, with legal, HR and privacy teams involved from the start and, where applicable, employee representatives.
It learns what is normal for each identity, in its role, and flags meaningful deviations such as an unusual query, a new system or a change in volume. Risk-based prioritisation then puts the most serious cases first, so analysts do not need to read every log.
Not every deviation deserves the same reaction. Options range from asking for additional authentication to restricting privileges for the session, ending it or escalating to an analyst. High-impact decisions should stay with people, and every step should be recorded.
Apply least privilege, remove access promptly when people move or leave, separate duties for sensitive actions and monitor behaviour. Agree the policy with legal, HR and privacy teams first, because monitoring colleagues must be proportionate and transparent.
Sharelock monitors behaviour after login, down to individual transactions and queries on critical applications, so misuse by someone with legitimate access stands out against their normal pattern.
Explore more terms