Automatic

Your encryption can be flawless, your code spotless — and your hardware can still give the game away. This episode breaks down side-channel attacks: the stealthy threat that turns processor quirks, power draws, and timing gaps into secret-spilling confessions.

Show Notes

Strong encryption and airtight code aren't always enough. Side-channel attacks don't target the data itself — they target the physical behavior of the hardware running the system, turning imperceptible signals like power fluctuations, timing differences, and memory access patterns into a blueprint for secrets. This episode of Automatic explores the mechanics and real-world implications of side-channel attacks, why modern computing trends are making the problem worse, and what security teams can actually do to fight back.
Here's what the episode covers:
  • What a side channel is — and why protecting data isn't enough if the behavior surrounding that data leaks clues to a patient observer.
  • Timing attacks — how fractional millisecond differences in processing speed can, across thousands of measurements, hand an attacker a roadmap to sensitive values.
  • Power and electromagnetic analysis — the way a chip's fluctuating energy draw during cryptographic work can be reverse-engineered to reveal what it was computing.
  • Cache and memory-based attacks — how shared processor caches in multi-tenant and cloud environments can let one workload silently observe another without ever directly accessing it.
  • Why performance optimizations backfire — speculative execution, branch prediction, and aggressive caching all create richer behavioral patterns that give attackers more to work with.
  • Defensive strategies — constant-time programming, hardware-level protections, process isolation, noise injection, and the critical importance of testing actual implementations rather than just auditing designs.
The episode's central argument is that security has to account for messy physical reality, not just clean algorithmic diagrams. Threat modeling needs to include who could observe a system and from what vantage point — and the right moment to address side-channel risk is during design, not after a system is already deployed and leaking. Retrofitting silence into a noisy machine is expensive; building quietly from the start is not.
For more from the show, check out the episode Why Multimodal Private LLMs Are Becoming the Enterprise Standard, which examines another dimension of how modern infrastructure choices shape security and capability tradeoffs.
Automatic

What is Automatic?

Agentic AI and automation from the perspective of whoever has to maintain it in six months. Where an agent genuinely belongs in a process, where a plain script is enough, how to design a handoff to a human, and what breaks quietly at scale.

Each episode takes one automation decision and reasons it through end to end — including the maintenance burden, the failure modes and the honest question of whether the process should exist at all. Written for operators and technical leads, deliberately free of hype. Five or six minutes an episode.

Topics include where an agent belongs versus a plain script, designing human handoffs, error handling and observability, maintenance burden, process mapping before automation, measuring what a workflow saves, and knowing when a process should be deleted instead.

Produced by Automatic.co, agentic AI and automation consulting. Full details, services and further reading at https://automatic.co