Darren P Meyer is a user on infosec.exchange. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Darren P Meyer @darrenpmeyer@infosec.exchange

The book that is mandatory reading at every data collection and aggregation company

The Veracode Research team is growing; we're looking for principal researchers for two roles for public-facing security researchers. Work on cool stuff, share it with the world!

1. searchjobs.ca.com/job/Burlingt

2. searchjobs.ca.com/job/Burlingt

I’m hiring a content developer for Veracode AppSec eLearning content; remote OK, nice perks including time for research projects

searchjobs.ca.com/job/Burlingt

"Delivering the Pen Test Report"

(can't find a good source, lmk if you know so I can credit)

Is there any event/party planning system that doesn't have a shit privacy policy?

It's frustrating enough when normies use "random" to mean "unpredictable" in technical contexts; it's inexcusable for a security pro to do that

Thinking of #EFail again: I don't think it's going to change anything.

Non technical people didn't use it until now and will not start using it.

Technical people understanding these issues will continue to use it.

Excel will support JS. The end is near.

I see the InfoSec nihilists are out again. 'customers only want likely threats, all else is waste' and 'breaches are basically random' and all that

It's not waste, threats are not random, you can make yourself less of a target; AND you could still be breached, should focus on response and recpvery too, etc.

Infosec is a bit like medicine.

You do what you can preventively to mitigate disease/hacks, but mostly you are going after symptoms. Treating the symptoms may work for a while, but eventually that won't work anymore.

Luckily, CVE names are easier to remember than gene and histone subunit names.

If it swore a lot, could also be mistaken for an infosec pro