Security that learns from every attempt
JournalTorus
What Lattice Guard does at three in the morning
Written by Priya Delacroix, Lead, Cost Control
Thursday, 31 July 2026
Attackers do not keep office hours, and neither should the systems that stop them. Lattice Guard watches access, secrets and patches around the clock, and every blocked attempt makes the next block faster.
Least access, kept current
Permissions drift. People change teams, services are retired, keys are copied into scripts. Lattice Guard compares what each identity can do with what it actually does, and suggests what to take away.
Patching without the drama
Critical patches are tested on a copy first, then rolled out region by region with an automatic way back. Most teams stop scheduling patch nights within a month.
Checked every hour
- Unused keys and tokens
- Public storage that should be private
- Machines missing critical patches
- Unusual sign-ins by location or time
Key takeaways
- Access should shrink as often as it grows
- Patch small and often
- Every blocked attempt is a lesson
What Lattice Guard does at three in the morning.
