Understory ranks No. 140 on Inc. 5000 list of fastest-growing companies in U.S. Read more about Understory on the 2026 Inc. 5000 list

Nancy Wang

Nancy Wang

Chief Technology Officer at 1Password

San Francisco, California, United States · Cybersecurity · LinkedIn profile

Nancy Wang is Chief Technology Officer at 1Password, based in San Francisco. On LinkedIn Nancy writes mostly about events and content and company news, most often as text posts.

37K+followers
84reactions on a typical post
207reactions on the best post
4 of 30recent posts worth featuring

Nancy's best LinkedIn posts

Recent posts that drew 100 reactions or more and say something a peer would learn from, most reactions first. Click any post to open it on LinkedIn.

Nancy Wang
Nancy WangChief Technology Officer at 1Password
Great to see Cursor announce their AIUC-1 certification. Disclosure: I sit on Cursor's Customer Advisory Board, and I've spent time in the AIUC-1 consortium pushing on what "secure" means once an agent, not a person, is running commands in your terminal. The real question isn't just whether an agent writes insecure code - it's who's acting, under whose authority, what it can access, and where a human needs to approve. AIUC-1 forces concrete answers to those, through adversarial testing plus an independent Schellman audit. It's the same thinking behind 1Password's work with Cursor: just-in-time secrets, no plaintext keys on disk, access governed by policy. Love to see things coming together like this. Congrats to the Cursor team on this milestone.
Image from Nancy Wang's LinkedIn post
Nancy Wang
Nancy WangChief Technology Officer at 1Password
Security was built for a world where developers were the bottleneck. Humans wrote and reviewed code, then deployed it and found the bugs. AI is removing the human bottleneck constraint. Now an engineer can generate in an afternoon what used to take weeks. At the same time, attackers can use the same tools to find and exploit vulnerabilities faster. The gap between how fast systems change and how fast security adapts is widening. That’s one of the ideas explored in AIUC-1’s latest paper, After Mythos: Defending at Machine Speed, which I was fortunate to contribute to. My contribution focused on a simple question: what does “assume breach” mean when systems, identities, and permissions are changing continuously? At the end of the day, it comes back to identity and access. If an identity is compromised, does the blast radius stay small? Are permissions scoped tightly enough to prevent lateral movement? Can you tell whether the controls you put in place six months ago still reflect reality today? What is changing is the rate of change: agents add more identities, more delegated access, and more automation. The underlying challenge remains the same: understanding who can access what, under whose authority, and then making sure that those assumptions still hold at any given point in time. Thanks to everyone who contributed to the paper, and especially Lena Smart for pulling me into the discussion. Mandy Andress, Neil Bennett, Manfred Boudreaux-Dehmer, David Campbell, Rajiv Dattani, Jen Easterly, Lars Falch, Bil Harmer, CISSP, CISM, CIPP, Erik Hart, Jimmy Heschl, Matt Hillary, Mark Hillick, Heather Hinton, Simon Hodgkinson, Rune Kvist, Dr. David Mussington, Daniel Nuñez, Kevin Powers, Rajiv Singhal, Phil Venables, Dan Walsh, Adeel S., Craig Weatherhead, Min Xu Ph.D, CISSP, Tom Zick, PhD., Emil Bender Lassen, Abby Shen, Scott Roberts, John I., Amyn J.., Katie Jenkins, Louise McElvogue, Omar Khawaja, Santosh Kumar, Xabier Muruaga, Rinki Sethi Ravi Soin ...and many more
Nancy Wang
Nancy WangChief Technology Officer at 1Password
Giving a coding agent a long-lived GitHub token is not an AI strategy. Instead, we're just creating a new standing-access problem. That was the design constraint behind 1Password for NVIDIA OpenShell, which launches today. Here's how it works: A developer picks a 1Password Environment, sets where the credential can be used and for how long, and approves the connection. With our integration, the agent never gets the credential and when it makes an approved request, the OpenShell Gateway swaps in the real credential, but only at the authorized destination. With how we've built this, the secret never touches the agent's context. That is the paved path we want for agents: access that is dynamic, scoped to the task, and removed when the task is done. Kudos to the NVIDIA OpenShell team Ali Golshan and John Myers, and the 1Password team Vinny Mannello, Matthew Porter, Matt Hoy, and KC Li for making this real 🔥

What Nancy posts about

  • Events and content40%
  • Company news27%
  • Industry analysis20%
  • Personal stories7%
  • Advice and playbooks7%

What makes the best ones work

  • Most of Nancy's best posts open with a plain statement of a view.
  • 33% of them carry an image.
  • They run long, often past a thousand characters.

Questions about Nancy Wang

Who is Nancy Wang?

Nancy Wang is Chief Technology Officer at 1Password, based in San Francisco. On LinkedIn Nancy writes mostly about events and content and company news, most often as text posts.

What does Nancy Wang post about on LinkedIn?

Mostly events and content, company news and industry analysis. Of the 30 recent posts we read, 4 drew 100 reactions or more with real substance.

What is Nancy Wang's most popular recent LinkedIn post?

The one that opens “Great to see Cursor announce their AIUC-1 certification.”, with 207 reactions and 7 comments.

Every post belongs to Nancy Wang. Understory is not affiliated with Nancy Wang or 1Password. We read public LinkedIn posts to study what B2B leaders write and what their audiences respond to, and the bio is our own summary. If this is you and you would like the page changed or removed, email alex@understoryagency.com and we will do it.

More cybersecurity thought leaders

See every cybersecurity thought leader, or the ads 1Password runs.

Want posts like these on your profile

We ghostwrite LinkedIn posts for B2B founders and executives, in their own voice, and turn the audience into pipeline.