Principle of least privilege

The cryptographic proof eliminates plausible deniability.

This brings us to our core operating doctrine, least privilege.

Lease privilege dictates that every user, application, and service account must operate with only the minimum permissions necessary to complete their job and strictly for the time needed.

If a junior analyst only needs read-only access to customer support tickets, granting them database administrator privileges is an architectural defect.

That cost them 400,000 euros in fines.

And when they appealed, the court basically said they didn't even try the concept of least privilege.

Today, that's what we're talking about.

Least privilege, best practices.

What does that mean exactly? And also, where do you start when everybody already has domain admin? Finally, we talk about role-based administration and why that's really the only realistic path here.

We talk about privileged account inventories, fire call accounts, segregation of duties, non-repudiation, and three backup roles that you should split apart before somebody quietly deletes your backup configuration.

My God, we've already spent 20 minutes on this.

So let's go.

So this is why it's essential that we give AI, especially ag- agents, their own identity.

That way, we can assign least privilege, ba- basically the minimum permissions necessary.

Segmentation is intensely important here, so only in the environments required for its function.

And I mentioned identity.

But I wanna give our, our listeners just kind of a forward-looking view of, uh, where this approach that we've talked today, whether that's segmentations, creating, you know, constrained or contained environments, w- where might that approach stop helping, and what risks would you leave listeners with to consider even after they've achieved the constrained access and segmentation?

Segmentation's critical, right? We, we've already mentioned that.

Least privilege, again, also helps dramatically reduce risk.

So segmentation and least privilege dramatically reduces risk.

We need to make sure to deliver access to the business.

But in the same time, we need, of course, to make sure for security perspective, to have least privilege.

But at the same time, we are so lack of context.

At the end, we are not running the business.

It don't know what it's going to use.

So for sure, you actually want to restrict it.

You want to start and just give it the minimum, the least privilege as possible.

And least privilege is difficult.

It's like, where does it, where do you draw, where do you draw the line? Where does it draw the line? Um, but yeah, as I said, sensible guardrails external to the thing itself, I think.

Uh, I mean, it'll, it's, it's effectively the principle of least privilege, which is realistically best practices, or best practice for all security, you could argue.

This is just another layer.

Yeah.