Skip to content

Blog

External Publication

3rd Element Consulting Featured in a ThreatLocker Customer Success Story

ThreatLocker featured 3rd Element in a case study on why a default-deny approach to application control earned a permanent place in our security stack.

Originally published at ThreatLockerRead the full case study at ThreatLocker

Why we adopted a default-deny approach

Dawn Sizer first saw ThreatLocker at an industry event and was drawn to its Zero Trust model: block everything by default, and only allow what's explicitly approved, rather than trying to catch every new threat after the fact. After a closer technical review, the team added it to the standard security stack.

Explaining Zero Trust in plain terms

Rolling out a new layer of control to existing clients meant explaining why it mattered, not just what it did. Dawn built a short explanation using a castle-and-moat analogy: once clients understood what was actually being protected and why, buy-in came easily, even for clients who initially saw it as an added cost.

What changed operationally

The tool closed a specific, recurring gap: employees installing applications outside of what's approved. Remote elevation removed the need to visit a site in person just to approve new software, and the vendor's own support response times have been fast enough that it doesn't slow the team down when something needs a quick decision.

Next step

Get a clearer view of your IT environment.

Find out what is working, where the risks are, and what needs attention next.