Welcome to ShieldedBytes, where cybersecurity meets clarity. This blog offers practical insights, best practices, and in-depth discussions to help you navigate the ever-evolving digital landscape securely.

Explore topics like data protection, network defense, secure coding, and more—all tailored for professionals seeking reliable, actionable advice.

Start exploring, stay informed, and take control of your digital security.

Fixing Session Fixation in a Remember Me Cookie

Rotating session IDs in an e-commerce API

The scenario

Our e‑commerce API was built on a stateless REST layer that delegated authentication to a central identity service. The API accepted a short‑lived bearer token (JWT) and, for convenience, exposed a “Remember Me” feature that let users stay logged in across browser restarts. The implementation was simple: the client stored a cookie named REMEMBER_ME that contained a signed, encrypted token. When the browser sent the cookie back, the API would issue a new JWT and refresh the cookie.

[Read More]

When a Critical CVE Slips Through

Lessons from a patch-delay incident in production

A remote‑code‑execution flaw in a third‑party JSON‑schema validator made its way into a live API last winter. The service was a Go‑based REST gateway, exposed to the public internet, and the CVE (CVE‑2025‑12345) let an attacker spin up code on the container host. The library’s fix landed in v2.1.0, but our pipeline still pulled v2.0.3. The attack happened before we even noticed.

Below is the real‑world story, what we did to stop it, and the trade‑offs we had to juggle. Grab a coffee, read on, and take notes for your own stack.

[Read More]

Prioritizing API Rate Limits with Attack Trees

Choosing controls after a DDoS incident

Attack‑Tree‑Driven Rate‑Limiting After a DDoS

We just survived a 2026 DDoS that hammered our public REST gateway. A botnet slammed a handful of endpoints with insane request rates, chewing through CPU and memory until real users hit time‑outs. The fallout was a frantic review of our throttling logic. Attack trees turned out to be the perfect tool to decide which endpoints need the tightest controls and how to enforce them without turning our API into a brick wall.

[Read More]

Finding Hidden Buffer Overflows in Rust Services

A practical guide beyond the null pointer

Rust’s ownership model and type system give developers confidence that many classic memory bugs are impossible. Yet, when a web service talks to the outside world—HTTP payloads, database rows, or binary blobs—subtle buffer overflows can still surface. These bugs usually come from unsafe blocks, FFI, or crates that expose raw pointers. In this post we dig into how such overflows arise in real‑world Rust services, show how to surface them with modern tooling, and outline practical mitigation steps that fit into a production pipeline.

[Read More]

Removing Malicious Binaries from a CI Pipeline

Spotting third-party artifacts before deployment

Why the problem matters

Modern CI/CD pipelines are a buffet of binaries pulled from package registries, container registries, or vendor sites. One bad apple can slip through, get signed, and end up in production. The 2025 “Supply‑Chain Attack” wave showed that attackers are hitting build tooling hard, not just the app code. If a malicious binary hides inside a Docker image or a shared library, it can survive across environments, dodge runtime defenses, and give attackers a foothold for lateral movement.

[Read More]

Enforcing GPG Signature Checks in CI

Stopping unsigned artifacts before production deployment

Why a Missing GPG Check is a Silent Vulnerability

When a CI pipeline builds a Docker image, compiles a binary, or packages a Helm chart, it usually writes the result to an artifact store. If the pipeline then pushes that artifact straight to a production registry or a Kubernetes cluster, the chain of trust is broken. An attacker who can tamper with the build environment, inject a malicious dependency, or simply mis‑configure a build step can get their payload into production without any alert.

[Read More]

How to Spot and Block Unauthorized Package Signing in Your CI/CD Pipeline

The threat of rogue package signatures

When a CI/CD pipeline pulls a dependency, it assumes the artifact came from a trusted source. In 2025, several high‑profile supply‑chain incidents showed that attackers can replace a legitimate package with a malicious one that carries a valid signature. The signature itself is not the problem; it is the trust anchor that the pipeline uses to verify it. If that anchor is compromised or misconfigured, the entire build chain can be subverted.

[Read More]

Tuning SIEM Correlation Rules to Cut False Positives on Azure AD Sign‑Ins

Azure AD sign‑in logs are a goldmine for detecting compromise, but they also flood SIEMs with benign events that look suspicious at first glance. A well‑tuned correlation rule set can reduce noise while preserving detection quality. Below is a step‑by‑step guide that balances precision, maintainability, and operational overhead.

1. Start with a Baseline: Understand the Noise Profile

Before tweaking any rule, run a 30‑day baseline to capture normal activity. Export the raw sign‑in logs to a CSV or a SIEM table and run a quick aggregation:

[Read More]

Reducing False Positives in Kubernetes Threat Hunting

Pruning noisy lateral-movement alerts

When an attacker gets a foothold in a cluster, the next move is usually to hop around pods, namespaces, or even nodes. Catching that hop is a staple of any Kubernetes security program, but the noise can drown you out. A single benign kubectl exec or a normal service‑mesh sidecar can set off the same alerts that a malicious container‑to‑container exfiltration would trigger. Below is a practical, repeatable walk‑through to cut the noise while still keeping the detection surface wide enough to catch the bad guys.

[Read More]

Securing Azure Service Accounts with Conditional Access

Using managed identities to reduce attack surface

Service accounts are the backbone of most cloud workloads. They give apps the permissions to read secrets, write logs, or call APIs. When an attacker breaks into one of those accounts the fallout can be huge. Azure AD Conditional Access (CA) and Managed Identities (MI) let you shrink that attack surface without breaking the automation you depend on. Below is a practical walk‑through of the most common patterns, the trade‑offs, and the troubleshooting steps you’ll hit in production.

[Read More]