Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
1–10 of 112 posts
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#2Yikes, Schemata and that delinquent CEO should be held accountable.
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#3Would it be possible to stop using aXXb nomenclature within the titles? Some of us aren't hip enough to know what all of them mean.
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#4a16z = "Andreessen Horowitz", for those not in the know. (The acronym is not expanded in the article. EDIT: OP has fixed the article.)
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#5Would it be possible to stop using aXXb nomenclature within the titles? Some of us aren't hip enough to know what all of them mean.
apologies, just a vc firm
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#6Would it be possible to stop using aXXb nomenclature within the titles? Some of us aren't hip enough to know what all of them mean.
Andreessen-Horowitz, who most people (and they themselves) refer to as a16z and have the eponymous domain name (a16z.com). They're one of the top VC firms on the planet -- exceedingly relevant to HN audiences and commonly discussed here.
Re: Securing a DoD contractor: Finding a multi-tenant authorization vulnerability
#7a16z = "Andreessen Horowitz", for those not in the know. (The acronym is not expanded in the article. EDIT: OP has fixed the article.)
fixed now