Chat Log from the May OWASP meeting with Jamie Dicken

This wouldn't fit in a comment, but there is a lot of interesting information in here:


Kevin Brown12:01 PM
the event was widely advertised at Fuse
Joe Kuemerle12:01 PM
Far NE Pennsylvania for me
Mosharrat Shams12:02 PM
Hi Everyone,
I am Mosharrat Shams.
Kevin W. Wall12:04 PM
I'm about ready to use a weed whacker to cut my hair. Two hour waits at Great Clips.
Going for that Lion look
Kris Wall12:08 PM
Since everything is going virtual, this has been a big advantage for under represented OWASP cities.

Greetings from Oklahoma City!
Scott Goette12:10 PM
Greetings from the north coast of Ohio
Chris Holman12:10 PM
Good afternoon from sunny Chelmsford, UK.
Andrew Fitzgerald12:10 PM
she's just so popular
Doron Samuel12:11 PM
Good afternoon! Greetings from New York City!
Bob Caruso12:12 PM
There is an extension available also that implements the Zoom-style grid (or Brady bunch).
Wolfgang Goerlich12:12 PM
Greetings from Detroit!
Bob Caruso12:12 PM
It has not been pen tested
Kyle Kline12:12 PM
This is my first Google Meet ever -- everybody's video was grainy, and I discovered in settings mine was defaulted to 360p max for both send/receive. Changing it up to 720p helped a lot :)
Klaus Agnoletti12:12 PM
I am from Denmark, so yes. Global
Kris Wall12:13 PM
New York, Detroit, UK, OKC! We might outnumber the Ohio folks!
Chris Brew12:15 PM
Hi Jamie, Chris Brew here from Facebook Seattle, working on the future Assistant that will live on AR/VR glasses. We have many lovely security challenges. More difficult to lose your glasses than to lose your phone, but it will happen.
Warner Moore12:17 PM
LOPSA Columbus is virtual tonight!
Kris Wall12:17 PM
Our BSidesOK conference is going virtual. We tried hard to make it in person. :(
Scott Goette12:19 PM
that's because she went into presentation mode
You12:22 PM
This chat has a lot of awesome. Not sure how to archive, but I might just try copy/paste
Newsletter I mentioned at
You12:23 PM
Scott Goette12:24 PM
Kris Wall12:26 PM
Valuable? Bah! What does it connect to? Where can it pivot?
Scott Goette12:27 PM
dev and qa are on your production network, right?

or does everyone practice network segmentation and not poke holes through firewalls?
Kris Wall12:28 PM
I've found plenty of half baked and abandoned apps with access to prod and internal DBs
Bob Caruso12:29 PM
Pivot-through is usually the biggest threat. spot on, @Kris Wall
Scott Goette12:35 PM
ooohh - like this. Different Security engagements should be appropriately timed for accuracy
You12:43 PM
Deployment too. Sometimes you have out of date third party components, and ops has to get involved.
Chris Brew12:47 PM
All of this makes sense in a big tech company context, except that it is not directly financial. Engineering resources are still limited, and over-committed, and there is still an aggressive timeline.
Kris Wall12:48 PM
I take this into consideration when sending my reports. Each remediation issue turns into an action item and each item has to be well-defined for the dev team.
Brandon Lewis12:49 PM
To add on to Chris' comment, it's still a lot of $$$ at the end of the day - rewrites are never cheap especially for large applications (refer back to estimates).
Warner Moore12:49 PM
Re-writes are almost never the answer.
Andrew Fitzgerald12:52 PM
+1 for "don't touch my tech debt"
Bob Caruso12:52 PM
I can see Bill's arms waving, but no sound
Chris Brew12:52 PM
A Facebook specific is that privacy is an extremely big stick to wield. No one can or should say no to a security person who has a justified privacy concern, because it is officially a non-negotiable priority. But dev teams still face all the prioritization issues you raise.
Warner Moore12:53 PM
Depends on the allocation. I typically like 20% for tech debt, security, etc.
If you'd prefer it not to be touched, it can be a smaller part of the pie. ;)
Kris Wall12:53 PM
Devs get upset if you can't define the problem. :)
Doron Samuel12:55 PM
I was about to say that point in the chat box :)
Bob Caruso12:58 PM
Scenarios are the most convincing when you can use the developer's own code (via pen test).
Kevin W. Wall1:02 PM
A great example of letting the perfect becoming the enemy of the good.
Jennifer Middleton1:03 PM
+1 ^
Bob Caruso1:04 PM
Also, developers are trained to not touch working code and are often measured/rewarded by shipping new features (tied to revenue) and not by remediations or weaknesses closed. SOLUTION: Put a $ value on remediations, and/or turn cybersecurity controls into product features that are advertised to customers so that they get pulled through the whole dev pipeline.
Kevin W. Wall1:07 PM
Great prezo. g2g to work mtg. Stay safe everyone.
Warner Moore1:08 PM
Security features in products is looking at it from a value creation perspective and not necessarily an operations perspective. A robust security program for a modern tech organization requires both security features in the products and security capabilities within the organization. Often, that distinction is missed which means the security program is lacking in an area.
Kris Wall1:08 PM
We need to be nicer?
Sure. I guess!
You1:09 PM
Maaaaaaaaaan, I was just working on being grouchier like Kevin
Brandon Lewis1:09 PM
As a dev (looking to transition into security), sounds like there's a big lack of security champions on the dev side - someone who can be a realistic bridge of communication/reason so it doesn't feel so "security versus app teams".
rachit sood1:09 PM
@warner +1
Ron Varghese1:09 PM
Nice work Jamie!
Nabeel Alauddin1:09 PM
Appreciate the tips to build partnerships/establish trust and enable dev teams to self-direct their security efforts
Thanks for the presentation, Jamie!
Ron Varghese1:10 PM
Brandon it depends on the maturity of the org.
Warner Moore1:10 PM
Fantastic presentation. Important and useful message to working more productively together.
Scott Goette1:10 PM
great talk!! empathy and understanding is key - hire more devs in security
Krysten J1:10 PM
Thank you for this presentation!
Bill Churchill1:10 PM
Thanks Jamie!
Bob Caruso1:10 PM
Thanks, Jamie
Scott Goette1:11 PM
Will you publish the deck that you presented?
Rebecca Harvey1:11 PM
Thanks Jamie!
Andrew Smith1:11 PM
Thank you, I appreciate your observations...especially around the golden rule.
Kris Wall1:11 PM
@jamie If we need to get more forceful with dev teams and their governance, let's say there's continual push back, do you have any suggestions for being effective and not burning bridges?
Robert Ravenscroft1:11 PM
As always, great job Jamie!
Warner Moore1:12 PM
Michael Flock1:12 PM
Thanks Jamie. Good stuff.
Brandon Lewis1:12 PM
Are the issues discussed here a really common experience for security folks trying to engage app teams?
Warner Moore1:12 PM
Kris Wall1:13 PM
Push back from dev teams is quite common.
Kris Wall1:17 PM
Scans are OK for finding low hanging fruit, but not a replacement for security assessments.
Bob Caruso1:18 PM
agreed, a scan is just the start. It should result in a systemic improvement
Kris Wall1:19 PM
Keep it going! Bust out the guitar!
Nabeel Alauddin1:19 PM
I have to dip out. This was my first OWASP gathering and I learned a ton. Thanks Bill for facilitating and looking forward to more sessions in the future.
You1:20 PM
Andrew Fitzgerald1:23 PM
We'll save the jamie snark for offline
Nathan Zender1:24 PM
πŸ‘ πŸ‘ πŸ‘
Brandon Lewis1:24 PM
Good presentation Jamie, thanks!
J.D. Santen1:24 PM
great job everyone.
Bob Caruso1:27 PM
Kris Wall1:27 PM
Thank you everyone!

Comments are closed