Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your CISO Doesn't Want More Findings. They Want Proof.

✓ Human-authored analysis; AI used for formatting and proofreading. You run a security scanner on your AWS environment. It finds 47 issues. The leaders hear: "our infrastructure has 47 things wrong with it." This is the problem with bug-finding tools. Every finding is bad news. What Amazon learned from a bank A finance company could not understand their own IAM policies. The policies were too…

Your security operations team scans your AWS environment and discovers 47 problems. When executives hear this, they perceive it as a list of issues that need fixing. However, a finance company learned from their experience that bug-finding tools only generate bad news. To provide assurance, they needed proofs instead of just finding bugs.

Amazon collaborated with a bank that could not manually reason about their IAM policies due to their complexity. Amazon formalized the semantics of the policy language and demonstrated mathematically what the policies allowed and disallowed. This helped the bank increase their workload and spending, as they gained confidence in their policies.

There are two types of information security tools: bug finders and property provers. Bug finders list the issues found in your environment, while property provers verify that no unauthorized principal can access sensitive resources. Executives want assurance, not just a list of problems. They want to confidently tell their board, auditors, and regulators that certain properties hold true across their entire environment.

AWS recognized this and developed tools to provide proofs. Property proving provides deterministic and reproducible evidence, which is valuable to CISOs and auditors. Running the same proof again yields the same result, giving the CISO confidence. Proofs enable fearless infrastructure rewrites and compound across services, providing global benefits.

The adoption of formal verification within Amazon started with pitching the idea to teams, who initially showed no interest. However, once adopted, proofs became a crucial part of their business strategy, enabling them to rewrite infrastructure confidently and cost-effectively.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

GitHub Actions Required property is missing: jobs

Required property is missing: jobs is the workflow parser telling you that the root of the file has no jobs key where it expects one.

  • Missing "jobs" key at root of YAML file
  • Workflow parser flags invalid-file annotation
  • Fix by ensuring "jobs", "name", and "on" keys at same level

Identifying Unclosed SQLAlchemy Sessions That Cause Connection Pool Exhaustion

Identifying Unclosed SQLAlchemy Sessions That Cause Connection Pool Exhaustion 1. The Failure Mechanism: Why Connections Were Never Released In web applications built with SQLAlchemy, proper session…

  • Unclosed SQLAlchemy sessions cause connection pool exhaustion
  • Manual debugging and code reviews ineffective for enforcing session lifecycle
  • Custom static analysis tool developed to prevent unclosed session patterns

More from Sunday 15 November →