What Makes a WAF High Assurance?
A high-assurance WAF needs explicit security requirements, bounded authority and evidence that its configured behaviour holds during both normal operation and failure.
Engineering notes
SELinux, Linux isolation and the architecture behind Sovereign Fortress. Explanations of the controls, their boundaries and the evidence needed to assess them.
A high-assurance WAF needs explicit security requirements, bounded authority and evidence that its configured behaviour holds during both normal operation and failure.
Linux security
How to disable SELinux, understand the security implications, and troubleshoot common problems while keeping SELinux protection enabled.
Read article : Disable SELinuxSELinux & Linux security
How labeled IPsec carries SELinux security context across hosts, how peer controls enforce policy, and how to verify a Libreswan deployment.
Read article : Labeled IPsecSELinux & Linux security
Compare SELinux and AppArmor: security labels, application profiles, policy enforcement, administration and practical choices for Linux systems.
Read article : SELinux vs AppArmor: How Do They Differ?API security
Practical API security: object authorization, token validation, resource limits and evidence that gateway and application controls work together.
Read article : API Security Beyond AuthenticationSELinux & architecture
How SELinux Type Enforcement, Linux namespaces and restricted capabilities constrain a WAF component's resources and privileges, and how to test those boundaries.
Read article : Protecting the WAF ItselfWeb & API security
Why WAF inspection still matters as AI-assisted attacks increase the need for behavioural context, API protection and policy-driven enforcement.
Read article : Is the WAF Obsolete? Why Signatures Alone Are Not EnoughThreat landscape
How AI makes technical knowledge easier to apply, shortens feedback loops and changes the cost and pace of cyberattacks.
Read article : Lower Barriers, Faster Attacks: How AI Changes the Threat LandscapeWAF architecture
How Web Application and API Protection (WAAP) combines inspection, behavioural signals and reputation, with policy turning observations into scoped gateway actions.
Read article : Security Signals, Risk Decisions and EnforcementSELinux & Linux security
How SELinux, seccomp, capabilities and namespaces constrain different parts of a container workload, with a Podman configuration and verification approach.
Read article : Seccomp and SELinuxVulnerability management
Why faster exploitation calls for exposure-aware prioritisation, temporary controls and verification of protection in running deployments.
Read article : The Shrinking Window Between Disclosure and ExploitationSELinux & Linux security
What seccomp filters can inspect, how their actions differ, and a runnable Linux example that rejects one syscall without terminating the process.
Read article : SeccompValidation & evidence
How client responses, gateway decisions and independent backend observations combine to verify WAF outcomes, including failures and inconclusive tests.
Read article : Testing a WAF: Why a Block Page Is Not Enough