Talk about insider threats and many founders become uncomfortable. They picture spying on employees and an atmosphere of suspicion. That is the wrong picture. Many insider incidents are not dramatic betrayals. They are a salesperson who forwards the client list to a personal Gmail account before joining a competitor, an accounts executive who emails a salary sheet to the wrong "Rahul", or a contractor whose VPN account is still active a year after the project ended.
The aim is not to distrust people. It is to design access so that one mistake, or one bad actor, cannot do outsized damage, and to do it in a way your staff find reasonable.
What counts as an insider threat?
CISA, the US cybersecurity agency, defines an insider as anyone who has or had authorised access to or knowledge of an organisation's resources, including employees, contractors and vendors. An insider threat is the potential for that person to use their access to harm the organisation, whether maliciously, through complacency or unintentionally (CISA: Defining Insider Threats). CISA groups them into types:
| Type | What it looks like | Typical Indian office example |
|---|---|---|
| Negligent | Knowingly ignoring security policies | Sharing a login with a colleague "to save time"; skipping updates |
| Accidental | Honest mistakes | Emailing a customer database to the wrong recipient; clicking a phishing link |
| Malicious | Deliberate harm for gain or grievance | Copying client lists or source code before resigning |
| Collusive | Insider working with an outside criminal | An employee paid to share customer data or OTP-related details |
| Third-party | Contractors and vendors with access | A support vendor's staff accessing more records than needed |
A well-documented example: Tesla, 2023
In August 2023, Tesla said that personal information of 75,735 current and former employees, including names, addresses, phone numbers, employment records and Social Security numbers, had been leaked by two former employees to a foreign media outlet. Tesla said they misappropriated the information in violation of its IT security and data protection policies. It sued the individuals, their devices were seized, and courts issued orders barring further use or sharing of the data (TechCrunch).
Lessons a founder can apply:
- Insiders do not need hacking skills; they need access that was broader, or lasted longer, than their role required.
- HR and employee data is as sensitive as customer data and deserves the same protection.
- Legal remedies exist, but they come after the damage. Prevention is cheaper.
Warning signs worth noticing
None of these proves wrongdoing. Together, and in context, they justify a closer, documented look:
- Large downloads or exports from CRM, ERP or file shares, especially shortly after a resignation.
- Forwarding of work email to personal accounts, or new mailbox forwarding rules.
- Access to systems or records unrelated to the person's job.
- Logins at unusual times or from unusual locations.
- Use of personal USB drives or unapproved cloud storage on work devices.
- Attempts to disable security software or obtain admin rights.
Behavioural cues, such as visible grievance, are sometimes cited, but be careful: acting on them without technical evidence can be unfair and legally risky.
Controls that work without insulting anyone
1. Least privilege by default
People get the access their role needs, and nothing more. Sales sees its own accounts, not the whole customer base. Developers do not need production database access to write code. Review access every quarter, with managers confirming what their team needs.
2. Offboarding on the last day, not next month
An employee's departure is a high-risk moment. Use a checklist owned jointly by HR and IT:
- Disable email, SSO, VPN and SaaS accounts on the last working day, or immediately for a hostile exit.
- Revoke access tokens, API keys and shared passwords the person knew; rotate the shared ones.
- Recover laptops, phones and access cards; wipe or reimage devices.
- Transfer ownership of files, mailboxes and cloud resources.
- Remove the person from WhatsApp groups used for work and from vendor portals.
- Review the last 30 days of downloads and email forwarding for unusual activity, as a documented, routine step for everyone, not a targeted one.
Apply the same checklist to contractors and vendor staff when their engagement ends.
3. Protect the data, not just the perimeter
- Mask sensitive fields such as Aadhaar, PAN and bank numbers in screens and exports where full values are not needed.
- Block or alert on bulk exports above a threshold.
- Restrict USB storage and unapproved personal cloud storage on work devices.
- Use data loss prevention rules for email attachments containing identity or financial data.
4. Log sensitive actions
Record who accessed, exported, changed or deleted sensitive records. The DPDP Rules, 2025 list visibility on access to personal data "through appropriate logs, monitoring and review" among minimum security safeguards (DPDP Rules, 2025). Logs also protect honest employees, because they show who did not do something.
5. Separate duties for money and master data
The person who adds a vendor or changes bank details should not be the one who approves payments. This blocks both internal fraud and external business email compromise.
How to monitor without breaching privacy
Employee monitoring in India has to respect privacy expectations and the DPDP framework, which applies to employees' personal data too. A proportionate approach:
- Be transparent. Tell staff in a written policy what is logged on company systems and why.
- Monitor company systems and accounts, not personal devices or private social media.
- Focus on actions (exports, access to sensitive records, admin changes), not on reading private messages.
- Limit who can see monitoring data, and log their access too.
- Set retention periods and delete what you no longer need.
- Take legal advice on your policy and on any investigation affecting an individual.
Culture is a control too
The cheapest insider control is a workplace where people report mistakes quickly. An employee who has just emailed a file to the wrong address should feel safe telling IT within five minutes, because recalling the message, revoking a shared link or asking the recipient to delete it works best immediately. If mistakes are punished harshly, people hide them, and an accident becomes a breach. Make the reporting route simple, thank people who use it, and keep disciplinary action for deliberate or repeated misconduct.
If you suspect an insider incident
- Preserve evidence quietly: logs, emails, device images. Do not let IT "clean up" first.
- Limit further access proportionately while you investigate.
- Involve HR and legal counsel early, and keep a record of every step.
- If personal data was exposed, assess CERT-In reporting and DPDP breach duties.
- Use a forensic examiner if the matter may go to court, so evidence is admissible.
How Cehpoint can help
Cehpoint's Managed SOC watches for the technical signals of insider risk, such as bulk exports, unusual access and new forwarding rules, on company systems, under a transparent policy agreed with you. When an incident is suspected, our cyber-crime investigation and digital forensics team preserves and analyses evidence in a court-admissible way. For the policies themselves, including monitoring and offboarding, see our DPDP compliance service.