Insider Threat Forensics

Insiders who cause real harm never make their presence known. Access continues to function after the employee's last day of work. An export runs mid-afternoon on a Tuesday. The archive gets built the night prior to an employee resigning. The investigation is made by taking the relevant records that already exist within the organisation (endpoints, servers and networks) and determining what these records will carry against named accounts, sessions and time frames.

◇ Footing first, then the bench time. It all begins with the free diagnostic, which is then followed by a written scope, and forensic fees must be paid before any actual examination can take place. Generally speaking, in most cases you only pay if we recover your data; the exceptions are electronic and mechanical failures, chip-level work, DVR jobs and forensic jobs. Full pricing can be found on the data recovery cost page.

// signs of an insider problem

What tends to prompt an investigation

What these are is how an uncomfortable feeling turns into instructions in writing.

Sign-ins are logged after somebody's final day of employment
Saved passwords, API tokens or SSH keys look to have gone with someone
Bulk exports have run against a database and nobody owns them
Archives were built and compressed in the days before a departure
Browsing history on a work machine is job boards and competitors
A personal device nobody recognises has joined the office network

Access that outlives the employment

Access lasts longer than most employers intend when an employee leaves. Copy a profile and the stored cache of credentials (which includes the password manager store) will be copied with it. Until they are revoked, all keys and tokens taken in the last week still work. A password viewed once over a desk works as well from a kitchen table. Thus, the first step is to identify what credentials were removed and then review both authentication logs and endpoint trace files until the systems reached can be listed by source IP address and hour. All events occurring after the departing date are included; this is commonly the part that decides it.

What the servers are sitting on

When considering endpoints as a source of data for an investigation, remember they are generally limited to providing half the information. On the other hand, query history can provide an overview of how data was extracted at scale; specifically the SELECT statement used to pull up a client's table, along with the timing and ownership by a particular account. When backups and snapshots are placed in tandem, it is possible to identify the time at which a record either changed or disappeared. The logs on a file-server will reveal what shares were accessed by whom, and where the first break occurred from an established pattern. Network activity and network captures may reveal sustained large-scale transfers to addresses that no business process within the organisation explains. In addition, server material deteriorates at a much faster rate than almost everything else; this is due to log rotation based on schedules (measured in weeks), and it is therefore placed atop the preservation list. Capture methods targeted at specific servers allow businesses to continue operating while the evidence is being preserved; this is particularly important when the server in question runs job costing.

Intent, evidenced instead of assumed

The tribunal will make its own assessment as to whether the evidence indicates careless error or intentional planning, so the investigation gathers all the information that speaks to it. Traffic on Teams and Slack regarding the move or the material. Compressed files (RAR or 7z) created over the past few days, which frequently retain their contents lists after being deleted. Job boards and competitor websites appearing in browsing history. Metadata with a last-modified-by value listing a named account against a named file at a specified hour. While individually none of these pieces of evidence is conclusive, collectively they generally are.

Private devices on the office network

Somebody's own phone or computer on your office Wi-Fi places us right next to a legal boundary, and we always remain on the lawful side of it. Whatever your network has recorded is company property and perfectly fair evidence: association times, the identifier of the hardware used, how much volume was carried and where it went. There is no way that we can examine the equipment itself without permission from the owner, a procedure agreed between solicitors, or a court order, and we do not take in any phones or tablets at all. Reports generated here are based on what the infrastructure lawfully shows, and they state where this boundary lies, which is exactly what keeps these reports useful.

The discipline of image creation behind this service falls to the forensic recovery hub. If the exit method uses a tenancy as part of that, see email and cloud exfiltration. Workstation deep imaging captures endpoints. Trade secrets would be covered on the IP theft page. Costs are listed on the prices page.

// what the work establishes

The findings an insider case stands on

These can link the account and its session to a time and trace it back into the systems' own logs.

Credentials

Which keys, tokens and stored passwords went, and when.

Access rebuilt

The systems reached with them, by hour and source address.

Exports

Extracting data on a large scale from databases and file servers, backed by query-based evidence.

Network

Steady outbound transfers to external addresses, out of logs and captures.

Planning

Messages, archives, browsing and metadata that speak to intent.

The boundary

What Wi-Fi records lawfully show about a personally owned device.

// the price, and who we may act for

Forensic fees, and the footing underneath them

The money, stated plainly

All instructions open at the free diagnostic stage. Allow 2 working days from the date a device reaches this bench. Forensic casework is not covered by our standard payment terms, where in most cases you only pay if we recover your data. The full forensic investigation including detailed forensic report costs £800 + VAT, payable 100% upfront before we start. A less expensive Forensic service is available that includes only the creation of a Forensic binary image and deleted-file extraction, and does not include a report; this option costs £400 + VAT. We do require all Forensic work to be paid for upfront. If a job requires us to investigate multiple servers then we will quote in writing once the free diagnostic is done. Both figures are listed on the pricing page, and no payment will be taken until a scope has been agreed in writing.

The footing we need

Insider instructions run on systems and files owned by the company, through HR or via a solicitor. Three doors in, and there hasn't yet been a fourth door. Kit owned by the business. A written direction from a solicitor, insurer or court. Or else a client-owned device, including those shared with another party in matrimonial matters. We don't hack here. We're not intercepting live data. Where a client has no right of access to see what's stored in a device, neither do we.

// getting your device to us

Getting it to the bench — plainly done

These cases generally start as a scoping call rather than a parcel. Ring 0800 689 0668 and explain to us what you are seeing; we can then provide you with an outline of what you need to preserve prior to this evening. We do not offer collection for items here. For any hardware that requires transportation (we only need the hard drives, not the machines), please contact us to obtain a quote first, after which it can be sent via tracked and insured post, or handed in at our Edinburgh premises Monday to Friday, 9am to 5:30pm, on a walk-in basis with no appointment needed. Once received in Edinburgh it will be booked into custody.

Still attached to a laptop, desktop, MacBook, iMac, server or CCTV/DVR unit? Remove the hard drive or SSD first. The bare drive travels on its own; when removing disks from a server remove all the disks and label each disk by its bay. This lab does not take machines apart. Any storage that has been soldered onto a motherboard (as in T2 and Apple Silicon Macs and a couple of thin laptops) will not be worked on: if it will not unbolt, we cannot work on it. If you're not sure what type of machine you have, ring us first. Phones and tablets are also not taken on.

  • Place bubble wrap around the drive then place inside of a rigid box or padded envelope. Pack as tightly as possible so that there are no loose objects within the container. Leave all cables, caddies and power supplies behind except for when sending an individual external drive. When posting an individual external drive, send it whole, in its housing along with its own cable and power supply.
  • Print off the shipping & booking-in form (PDF). Write down your name, mobile number, and a brief description of what occurred. Place this document into the same package as the drive.
  • The Royal Mail Special Delivery service offers both tracking and insurance from door-to-door. Using your own courier service will achieve the same results.
  • Want to hand it over yourself instead? After receiving your quote, reception will accept drop-offs at the address below, Monday to Friday, 9am to 5:30pm, with no appointment needed.
// where your device is headed

Edinburgh Data Recovery

4 Redheughs Rigg
Westpoint, South Gyle
Edinburgh, EH12 9DQ

↓ Print the shipping & booking-in form (PDF)

Your parcel should be addressed to Edinburgh Data Recovery, approximately two and a half hours (and 130 miles) from Aberdeen via the A90; alternatively it can reach us the next working day by tracked post if this journey time / distance is prohibitive to travel. As soon as your drive has been scheduled in we will contact you.

Still unsure about what should be placed inside of the packaging? Please call us first on 0800 689 0668, or use our free online diagnostic tool to assist you in deciding which items belong inside of the packaging before sealing.

// insider threat · asked before instruction

What boards and IT leads want answered

Generally, session records, source addresses and authentication logs will usually answer which account it was; where it originated from; when; and what it interacted with. Save those logs now because log rotation is going to delete them according to its own schedule, and remove the access once a capture exists.
Rarely, and we never collect one. Most of our time on the server side is doing very specific tasks: exporting logs; taking database snapshots; creating an image of the named volume; all taken into hash-verified files with your IT team present and generally without any downtime. The specifics of what will be taken and why are documented in the written scope.
Not without some form of consent, an agreed upon protocol or a court order. This computer belongs to them. However, the information about what your own network captured regarding the activity of this computer belongs to you. Association times, volumes carried and destinations reached often provide enough evidence to make the point, without anyone having to touch the device.
No. Rotation was the correct security choice, and the history survives it. Query records, endpoint traces and logs all still indicate what those credentials were used for while they still worked. It is now important to get the whole lot preserved prior to routine housekeeping thinning it out.

Your own systems wrote it down. We read it straight back.

Save those logs before they are rotated. The freephone connects you directly to an examiner, not a queue.