Lea Kissner

Lea Kissner

@leak.bsky.social

Security, privacy, respect. Was the Twitter CISO until it was terrible. Now LinkedIn CISO. they/them

8.1K followers104 following878 posts

The eMudhra "don't trust this trusted cert" vulnerability situation added insult to injury: this is actually a time where connecting to random wifi could be a security issue*. Usually this is terrible security advice! * If your OS and all the apps caching their own trusted you certs aren't fixed.

Uh oh, Amazon has uncovered my deepest darkest secrets.

Dexerto@dexerto.bsky.social

Amazon users are discovering a bizarre "About You" page that reveals what the company thinks it knows about them One woman found Amazon had determined she "has flat buttocks"

"Building Safer Technology: A Field Guide to Failing Well" is here and you can get it wherever books are sold (35% discount code for you in this thread). I've spent 20 years dealing with terrible things on the Internet and I've learned a lot about how to build things which really *work*.

View full thread

Discount code SAFERTECH confers a 35% discount off the list price of ISBNs 9780135589328 or 9780135589359 only when purchased on informit.com. Discount does not apply to “Best Value” or “Additional Savings” book + eBook bundles. Offer expires 11:59pm EDT May 31, 2027.

informit.comInformIT: The Trusted Technology Source for IT Pros and DevelopersResources from the authors, creators, innovators, & leaders of technology - home to leading publishers Addison-Wesley Professional, & Sams.

Discount may not be combined with any other offer and is not redeemable for cash. Offer subject to change. (Yes I am required to post that whole schpiel)

"Building Safer Technology: A Field Guide to Failing Well" is here and you can get it wherever books are sold (35% discount code for you in this thread). I've spent 20 years dealing with terrible things on the Internet and I've learned a lot about how to build things which really *work*.

View full thread

Go beyond theory and learn to implement safety practices directly into your workflows and organizational structure. This book provides concrete tools, mental models, and communication strategies for individuals and team leaders to build products that can withstand real-world chaos.

You'll learn how to prevent failures and also how to manage them gracefully when they inevitably occur, preserving trust and turning crises into powerful learning opportunities.

"Building Safer Technology: A Field Guide to Failing Well" is here and you can get it wherever books are sold (35% discount code for you in this thread). I've spent 20 years dealing with terrible things on the Internet and I've learned a lot about how to build things which really *work*.

Technology is changing fast. So are humans. Software and AI are woven into everything from power grids to the devices in our homes, failure is no longer a minor inconvenience―it's a critical business risk that can cost lives, paralyze economies, and erode trust.

Building Safer Technology delivers a practical field guide to safety engineering, a practice dedicated to designing systems that are not only innovative but also fundamentally resilient. We teach durable thinking that works even as technology and the ways we interact with it change.

The Pinterest office has a really nifty 📌 giant red pushpin made of Lego📌 They were kind enough to invite me to speak yesterday and had over an hour of great questions, so I'm pretty sure that they liked the talk.

I can't believe that our book, "Building Safer Technology: A Field Guide to Failing Well" is here NOW. Learn how to build safely -- security, privacy, trust&safety, AI safety, etc. We concentrate on the underlying thinking and skills so this is durable knowledge even as technology changes.

Did I mention that we've been writing a book? Fundamentally, security, privacy, trust&safety, AI safety -- all the fields aimed at dealing with dealing with how technical systems hurt people and how to avoid it -- share a foundation. We cover how to think and achieve *truly* effective practice. 1/

View full thread

Did I mention that we've been writing a book? Fundamentally, security, privacy, trust&safety, AI safety -- all the fields aimed at dealing with dealing with how technical systems hurt people and how to avoid it -- share a foundation. We cover how to think and achieve *truly* effective practice. 1/

View full thread

Did I mention that we've been writing a book? Fundamentally, security, privacy, trust&safety, AI safety -- all the fields aimed at dealing with dealing with how technical systems hurt people and how to avoid it -- share a foundation. We cover how to think and achieve *truly* effective practice. 1/

View full thread

... like metrics that drive effective action (and not perversity), communication, and team design. I had to learn all of these things the hard way, both on my route to Distinguished Engineer and as a CISO. This is the book I wish I'd had and I hope it helps you, well, build safer technology. 3/

I've been lucky to work with amazing people in my career and on this project. Yonatan Zunger and I have worked together for nearly two decades and have been meaning to write this book for over 10 years. We also have Phillip Misner, JP Hernandez, Harmony Mabrey -- and the inimitable Danielle Cass. 4/

Did I mention that we've been writing a book? Fundamentally, security, privacy, trust&safety, AI safety -- all the fields aimed at dealing with dealing with how technical systems hurt people and how to avoid it -- share a foundation. We cover how to think and achieve *truly* effective practice. 1/

_Building Safer Technology: A Guide to Failing Well_ covers topics all the way from design to incident response to programs all the way to the nitty gritty critical things that no one talks about but are so often the difference between good intentions and effective impact. 2/

What *does* a hacker look like to you? I probably shouldn't admit how many black hoodies I own, should I? (Spy Museum in NYC, BTW. My kids loved it.)

I can't really walk this week for mysterious reasons* and boy is my dog happy with my inability to get into the office. * Literally I don't know why and the doctor doesn't have appointments for weeks. Please feel free to suggest good concierge doctors around Mountain View this is silly.

View full thread

Holy crow does the security field need people who are willing to say "I don't know, let's figure it out" and understand the systems in enough depth to figure it out. We don't know how to handle security sustainably yet in this shifted threat landscape... let's figure it out.

Note that this means that not every job in security is likely to be in equal demand. The system-oriented, figure-it-out jobs are much more valuable in a world of LLMs than a more structured job. That's not unique to security, but it's still true for us.

The rate of supply chain attacks is bonkers. Right now we're seeing hundreds in a week when about a month ago 7/week was notable. Coding agents, like humans, are not perfect and don't write perfect code -- they also tend to do wild things and effectively attack your internal systems in the process

The most effective way to deal with most of these things is with really solid engineering-oriented security, making the underlying systems work better as well as more safely. Using LLMs can help us investigate potential incidents and pay down technical debt and build security features but...

I have learned a valuable lesson thanks to a Little Free Library in my neighborhood: the Daily Mail and I do not agree on what makes a good novel.

Companies are much more transparent about security and reliability bugs than privacy bugs. I've wanted solid data on this for a decade, but it's effectively impossible to get. 1/🧵 Obligatory notice: I'm not speaking about or on behalf of my employer. I'm speaking as someone who founded PEPR

Data Bear 🏳️‍🌈@dataandpolitics.net

Tech engineering normalized transparency (status pages, postmortems, bug disclosures) partly to encourage other industries to do the same. Decades later it’s backfired: people hear our issues but not their own industry’s, so they assume engineering is worse rather than more transparent.

View full thread

For similar reasons it's very, very hard to get data on privacy engineering topics. I really hoped that the European Data Protection Authorities would capture data from incident disclosures with eng info, but given that they're getting free-form data from lawyers this seems unlikely. 6/

Right now, pretty much the only way to learn about these topics in practice is to go to PEPR (the Privacy Engineering, Practice, and Respect conference) or to quietly ask someone you know in the field. I'm glad we have a conference (it's June 1!) but ... www.usenix.org/conference/p...

usenix.orgPEPR '26The 2026 USENIX Conference on Privacy Engineering Practice and Respect (PEPR '26) will take place on June 1–2, 2026. PEPR is focused on designing and building products and systems with privacy and res...

Companies are much more transparent about security and reliability bugs than privacy bugs. I've wanted solid data on this for a decade, but it's effectively impossible to get. 1/🧵 Obligatory notice: I'm not speaking about or on behalf of my employer. I'm speaking as someone who founded PEPR

Data Bear 🏳️‍🌈@dataandpolitics.net

Tech engineering normalized transparency (status pages, postmortems, bug disclosures) partly to encourage other industries to do the same. Decades later it’s backfired: people hear our issues but not their own industry’s, so they assume engineering is worse rather than more transparent.

View full thread

Security has built a culture where the expectation is that there is a certain level of discussion. If you disclose an issue competently, I may well end up believing that you're more competent rather than less. 4/

When I worked at Google it was much, much easier to talk publicly about, say, the sophisticated XSS that someone found. It required bouncing it off an XSRF in an entirely different surface. If this is the only XSS you have in ~2014, you were doing pretty well. Everyone got to learn, it was great. 5/

Companies are much more transparent about security and reliability bugs than privacy bugs. I've wanted solid data on this for a decade, but it's effectively impossible to get. 1/🧵 Obligatory notice: I'm not speaking about or on behalf of my employer. I'm speaking as someone who founded PEPR

Data Bear 🏳️‍🌈@dataandpolitics.net

Tech engineering normalized transparency (status pages, postmortems, bug disclosures) partly to encourage other industries to do the same. Decades later it’s backfired: people hear our issues but not their own industry’s, so they assume engineering is worse rather than more transparent.

Speaking about privacy is much harder. For several years PEPR couldn't find anyone to speak about how to do privacy incident response because it was really only done at large companies who were afraid to admit that there even *were* incidents. Can you imagine this happening in security? 2/

(Eventually I could speak because I was working at a startup and they were happy to advertise that they had serious security/privacy chops wildly out of proportion to their size.) 3/

Are you a privacy engineer or work with privacy engineers? Would you like to learn more about probably engineering? Boy do I have a conference for you! PEPR, the conference on privacy engineering, practice, and respect, is happening June 1-2 in Santa Clara, CA. www.usenix.org/conference/p...

usenix.orgPEPR '26The 2026 USENIX Conference on Privacy Engineering Practice and Respect (PEPR '26) will take place on June 1–2, 2026. PEPR is focused on designing and building products and systems with privacy and res...

Spotted in the San Jose airport TSA bins: Delve comparing themselves to the TSA. Given the accusations leveled at Delve, I'm very amused by "AI can't prevent a secondary pat-down but it can find your SOC 2 evidence"

A few of us are (finally!) in the last stages of editing a new book 🎉 and the tentative title is "Creating Safety: How to build with new technologies without shooting yourself (and others) in the foot" Good title? Have a better one?

Security folks: have we considered *not* releasing security patches for the avalanche of bugs we're about to deal with? Hear me out. Given how much faster it's getting to reverse engineer an exploit from a patch and that we're expecting to fix *so* many bugs at once, maybe do a full release.

Add a bunch of chaff in the form of non functional but potentially-interesting changes to slow things down and hopefully people have more time to, say, update iOS or Linux before the exploits are out there. Just a thought.