securing something somewhere

Boston, MA
Forgot I unfollowed everyone way back when 😳 if you see a "new" follow from me that's what happened.
90
Imagine telling a company that if you build an offensive security product, you must build a defensive one to counteract it. That's effectively what everyone saying we need to distribute security models to defenders is not saying out loud...
1
6
...how would we even do that? Regulation? That's what these companies want. I don't agree with gatekeeping for offense, but it's a slippery slope to start mandating orgs on to whom/what to build/sell. If a company wants to create an open defense model they could just do that ...
1
5
...but won't because the existing crop of security companies are not AI companies. They need to sell their product and make it better so the models will be tucked away behind them (and there has been AI/ML models baked into products pre-LLM that weren't being made available).
6
Ross Nanopoulos retweeted
“Patch the planet, we can fix everything” is one of the most misleading, and harmful security initiatives I’ve seen. As if spending billions of dollars cooking the oceans to run swarms of agents spinning their wheels applying hourly? minutely? patches on every abandoned instance across the planet, racing against every incompetent sysadmin - no you will never catch up with human stupidity. And it’s completely the wrong direction. It’s this old school mentality that “I’ll stay in my IT lane, and just update every package and infra” as if this will ever amount to anything. As if this hasn’t been the strategy for half a century. Obviously you’re supposed to patch. But why be a hamster in a wheel spinning idly, while incompetent devs slop-cannon millions of lines of some of humanity’s most atrocious code ever conceived, bypassing every security recommendation, every known best-practice, to meet an arbitrary deadline set by their private equity overlords to ship some inane b2b saas that nobody is going to use, but will get everyone’s data leaked. You won’t patch everything. You won’t catch every bug. You know it’s stupid, it’s a helpless strategy because you don’t want to address the real root cause: making software that doesn’t suck ass. Engineering principles that aren’t guided by psychotic greedy men in suits that just want a return on their investment at the cost of everyone’s data. The problem is nobody gives a shit about breaches. “Cyber insurance covers this”, you send the breach notification, everyone shrugs as if it’s the accepted cost of living in society. So companies have no incentive to care. Some of the most incompetent passionless people become “engineering leaders” that “understand the business” of shipping atrocities, without an ounce of consideration or thought, pure monkey level poop-slinging. The worst code you’ve ever seen is production code, self-merged by the guy thinking increasing shareholder value is how you barely make it across the retirement line. “Move fast and break things” has been one of the most dangerous principles, and an embarrassing one to hold today. We have solutions. The dumbest dev can still ask a coding agent to find, explain, and address security issues in software architecture, and in implementation. And it does a better job than the majority of security engineers I’ve worked with. But they do the opposite. They go AROUND and bypass every security recommendation anyone or anything makes. I’ve seen Claude-generated comments in code saying “this is highly insecure but we have decided to accept the risk” for things with trivial fixes. God forbid, you’re going to have to work with devs. Teach them software design, architecture, planning how components and microservices interact, how to make safe code, how to keep it safe, ultimately just to be considerate. To care a little bit about your craft. “Patch the planet” is a waste of time. Invest in what we ship instead. It’s the ONLY way to make software resilient.
26
45
285
10,904
Ross Nanopoulos retweeted
When we can ship substantial improvements in days instead of months, we should ask more around “how great can this be?” rather than “when will this get done?” Stop treating a pursuit of excellence as a threat to speed. Moving fast should raise standards instead of lowering them.
9
13
124
6,984
always was ❤️🔒
maybe the point of cybersecurity was the friends we made along the way
1
140
people really be acting like once all the software vulnerabilities are fixed we've solved cybersecurity 🫠🫠🫠
9
I know...I messed up my cybersecurity awareness month streak, but I feel like we are all aware enough now, right?
7
Why do all the @1Password integrations only let you use a personal/family account? I feel like the biggest use cases are b2b right now, except probably Muse.
1
59
Ross Nanopoulos retweeted
Full content from our security engineering workshop @BSidesNYC is at seceng.guide/
7
36
236
9,201
Day 16 of cybersecurity awareness month: last night's meetup discussed onsite wifi security using github.com/nzymeorg/nzyme (i.e how to detect those toilet paper TV devices) While you can analyze your packets with it at home, your risk profile probably just needs some basics:
1
1
63
Change default SSIDs and passwords Use WPA3 (or WPA2 at minimum) Isolate guest and IoT networks Regularly update firmware Disable any unneeded features like WPS, UPnP, Remote Access
15
Ross Nanopoulos retweeted
🎙️ @andrewbecherer on the Build vs Buy decision for security teams in the agentic AI era
1
5
9
2,096
need to get the roadster to the @berrics
Do a kickflip!
15
Ross Nanopoulos retweeted

Tesla

Roadster

3,021
12,445
94,706
4,189,405
Wow I haven't been in Kendall Sq. in forever. Who was going to tell me there is so much going on now?
65
Day 15 of cybersecurity awareness month: support local meetups/conferences! Boston, see you @securitymeetup tonight? Also check these out: @OWASPBOSTON @BASConf @defcon617 @Layer8Con @MinuteConBoston @SecurityBSides Cambridge, MA coming up Oct. 25: bsidescambridgema.org/
1
111
Building software in Go with AI has been a delight. Given the number of high quality open source projects and the simplicity / opinionated nature of how to write Go code, the training data for models is highly representative of what good looks like and the outputs show it.
Google created Go Cloudflare uses Go Uber uses Go Dropbox uses Go Twitch uses Go Docker is written in Go Kubernetes is written in Go Prometheus is written in Go Terraform is written in Go Fast compilation. Simple concurrency. Built for infrastructure. Why is Go still underrated among developers?
1
1
29
Ross Nanopoulos retweeted
🏴‍☠️ Ahoy InfoSec practitioners! The CFP for #BSidesSF 2027 is OPEN! Got research, a talk, or hands-on workshop to share? Bonus points if you tie it to our theme: Pirates! 🦜 📅 Deadline: Nov 9, 2026 📍San Francisco: April 3 & 4, 2027 Submit here👇 pretalx.com/bsidessf-2027/
2
5
13
947
I mean...quite obvious...most startups are by default incorporated in Delaware.
Delaware had the highest share of Ramp businesses paying for an AI product or service in September: 72.7%.
1
2
61