Embracing an Adversarial Mindset for C++ Security Amanda Rousseau 9/18/2024 This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY1 cross-org issues to combat a whole bug class 15% ● Writing tools to help with discovery 4%Adversarial Mindset Not taught in traditional institutionsThinking Like an Adversary Challenging assumptions Creatively libraries: • clang_rt.fuzzer_no_main-x86_64.lib • libsancov.libImportance of a security-focused mindset Considering security from the start of a project Threat modeling at the design stage Know the

The Outward Mindset Think about: The People in your life you most like Your Best Boss The person who Inspires you to do your best The acquaintance you most respect KCPD Swat Team Taking criminals down Share? Inward Mindset How can this affect a Contract proposal process. i.e. What do I need to do to win business vs What do I need to do to provide value to the warfighter Inward mindset at work “Nice” “Nice” inward mindset Outward mindset CFS2 – Debt Collection. Berate Debtors until they pay vs Find help for Clients so that they can pay San Antonio Spurs 13/20 in 1st place -Players who have “gotten

Benefits Drawbacks CI Triggered and GitOps Owned Benefits Drawbacks A Mindset Shift Conclusion The Path to GitOps | 4 Contents 37 Chapter 7–Handling Secrets Common Kubernetes space. Specifically, continuous integration (CI) and continuous delivery (CD) tooling. My mindset at the time was, “We can do better.” We had new, declarative tools for infrastructure and a new this. A Mindset Shift Using GitOps with CI/CD calls for a shift in thinking. Traditionally, you think of promoting code or images into environments. But GitOps with CI/CD changes that mindset. When working

successful companies are often those who treat it as a new paradigm. This leads to an experimental 
 mindset and an iterative approach that gets to value faster and with greater buy-in from 
 users and stakeholders apply across all markets. The common theme: AI deployment benefits from an open, experimental mindset, backed by rigorous evaluations, and safety guardrails. The companies seeing success aren’t rushing

people outside of their team. This bakes in security from the get-go and allows a security-first mindset even when developers are working on an MVP. Everything we do is based on Zero Trust architecture management, everything happens in Git…. Everything is founded on that infrastructure as GitOps mindset where your design stays in Git, and everything is in Git. Your production or staging environment

complicated... Choose the smallest amount of work that you can write a test for "Engineering" mindset "Hacking" mindset Courtesy of Phil Nash 82TDD is difficult... Takes dedicated practice Requires a new

together Instant evaluation Grow furtherTransformation Resistance low with others Contagious Mindset Each others’ support Let’s try it out!Quality Ownership Knowledge Evolution Transformations

long-term productivity ■ Improves safe development in other languages ■ By adjusting developer mindset 13 “Once you learn Rust, you are one with the borrow checker — it never leaves you. I now see

in control flow State Machine Comes in to Rescue • Simple is beautiful! • A divide-and-conquer mindset to simplify logic • Sort out a limited numbers of states • Define conditions of transition • Focus

business outcomes rather than operating an order-taking function. This shift in organizational mindset is critical to any successful technology transformation but requires substantial changes in behavior