What is the principle of least privilege?
In this brief video, Sagiss co-founder Jim Lancaster explains the principle of least privilege: why it matters and how you can incorporate it into your company's IT security plan.
Below is an adapted transcript of the embedded video.
What is "least privilege"?
The principle of least privilege is all about controlling access to data and making sure that only the people who need access to data actually have access to that data.
For example, the people in sales only have access to sales data and the people in accounting only have access to accounting data. It’s a way of partitioning off your data into ‘islands’ so if one area is breached it doesn’t mean that the whole system is breached.
Implementing the principle of least privilege
The reason some companies struggle to implement least privilege is that they’ve been doing things wrong for a long time, so they’ve got a very unorganized pile of data out on a server or similar system. Instilling or retrofitting some sort of organization on top of it seems like a challenge.
The first step is always the hardest.
How we generally approach least privilege is to create a new structure and then move the data into the new structure and work through any issues. In the end, least privilege is something everyone should implement because it’s really all about protecting data and corporate information: protecting it from ransomware, from malicious outsiders, and from employees gaining access to things they shouldn’t. It’s really very important that companies implement something like this.
A rule of thumb for us is never to grant privileges explicitly to an end user; you always grant privileges to a group. That way you know who has access to what by their group membership.
This is all built into Windows Active Directory. It’s part of Windows server and it’s very simple to administer. It’s available to everybody.