Chris Dorros Email & Phone Number

South San Francisco, California, Us

I'm responsible for the Security Infrastructure organization at Stripe. Our mission is to protect Stripe systems & data. We do that by building core security primitives that achieve uncompromising security, are consistently applied, and are simple to use. We aim to integrate security so tightly into the foundation that engineers need not worry about the security & privacy of their code.Over the years, I've grown the Security Infra org from 5 to 40+, spanning Cloud Security, Web Frameworks, Zero Trust, Secrets, PKI, Identity & Access Management.My opinion is that most organizations do not spend enough time on Least Privilege systems design. Stripe is different. I'm proud of what we've built at Stripe to protect the security and privacy of our users' data.

San Jose, Ca, Us

Led multiple security software engineering teams at Cisco, focused on building security infrastructure exposed as self-service APIs for all Cisco product teams.A sample of the projects we built and operated in production:* Automated SSL/TLS certificate generation & deployment, backed by Let's Encrypt* Distributed secrets management, based on HashiCorp Vault* Identity Broker (IDB), extending existing IDP solution for API & CLI workflows, based on OAuth 2 & OpenID Connect.* AWS Security Visibility, detecting security issues and delivering telemetry straight to development teamsAside from the infrastructure development efforts, I worked to build the security program for a new organization inside Cisco, establishing partnerships across the various security teams. I am a big believer in decentralized security - that is - having teams operating in a DevOps model own their security, so we focused on providing services like pen-testing, threat modeling, and automated security tooling vs handing teams a checklist and a mandate.

San Jose, Ca, Us

I joined OpenDNS to help build out the security team. This was my first experience at a startup that was undergoing rapid growth (tripled in size in one year), developers moving very fast (100+ pushes to production/day), and sheer scale (processing DNS request count ~45x the number of Google searches/day). This environment is becoming much more common today, but it required a radically different approach and solution than most market products offered.We approached the security problem by an intense focus on helping over telling. We spent our time building software and tools that worked at our scale, submitting pull requests for security improvements, and sitting side-by-side with the product teams. This bias-to-action, enablement approach led to developers actually seeking security help from our team, flipping the classic security vs product problem on its head.Some of the fun technology I got to dig into included:* Cloud HSM. Short-lived certificates. Key signing ceremonies. Reading the X.509 spec too many times.* AWS - became go-to expert in engineering.* Docker* Linux. FreeBSD.* Terraform, Packer, Ansible* Secrets managementWe were acquired by Cisco in August of 2015!

Pasadena, Ca, Us

* Lead security engineer and security project management for Mars Science Laboratory "Curiosity Rover" project ($2.5B)* Security research for DoE Smart Grid Regional Demonstration Program (partnership with Los Angeles Department of Water and Power)

Pittsburgh, Pennsylvania, Us

* Research in malware network traffic analysis* DHS software vulnerability database cleanup effort

Bethesda, Md, Us

Network and systems design, implementation, and administration for F35 Fighter Jet Training Systems Project

Master Of Science (Ms), Information Technology - Information Security

Bachelor Of Science (Bs), Computer Engineering