Showing Post From Security
Chaos engineering in 2026: revisit Chaos Mesh, LitmusChaos and Krkn before you break another thing in production on purpose
Most teams first meet chaos engineering as a slogan: break things on purpose. Somebody installs a chaos tool, deletes a few pods in staging, sees them come back and declares the platform resilient.
Read moreData catalogs in 2026: revisit OpenMetadata, DataHub and Apache Atlas before you add another metadata platform
Most teams do not decide to build a data catalog. They drift into needing one. A new analyst asks which of three “orders” tables is the real one.
Read moreWeb application firewalls in 2026: revisit ModSecurity, OWASP Coraza and BunkerWeb before you put another WAF in front of your app
A web application firewall is one of those things that gets added after a bad week. A penetration test report arrives, or a customer sends a security questionnaire with a line that says “Do you use a WAF?
Read moreStatic code analysis in 2026: revisit Semgrep, Opengrep and SonarQube Community Build before you add another code scanner to CI
Most teams add a code scanner to CI in an afternoon. A YAML job, a default rule pack, a green tick.
Read moreSchema registries in 2026: revisit Confluent Schema Registry, Apicurio Registry and Karapace before you ship another event schema
An event schema looks harmless in a pull request. A few fields, a namespace, maybe a default value. But once a producer starts writing with it, that schema is a contract with every consumer that reads the topic today and every consumer that will replay it next year.
Read moreRuntime security in 2026: revisit Falco, Tetragon and Tracee before you trust another runtime alert
Most teams now scan images before they ship and check manifests before they reach the cluster. Then the container starts, and for many of us the story stops there.
Read more