News for hackers. Stuff that matters.
Re:Npm security post-mortem by tptacek on Friday March 21, 2014 @03:54PM (#7444484)
Don't scope projects based on lines of code; you'll get shafted. Figure out the attack surfaces (for instance, how many app endpoints, how many URL routes, how many roles), come up with a total person/weeks scope, and then (especially if it's your first project) triage: capture the most important attack surfaces in a "pilot" or "90%" project to figure out how well you work with outside security teams.

A good firm will help you do this, gratis, if you're serious about funding the work. We do it "on spec" for most of our clients, even though that work sometimes ending up helping a competitor deliver the project.

It's fine if firms ask you for lines-of-code counts, but if that's the only question they ask, I'd consider that a red flag.

Re:Npm security post-mortem by giovannibajo1 on Friday March 21, 2014 @08:46PM (#7446220)
Thanks for the heads up. I had actually mentioedn only KLOCs as an initial number just to have a rough idea; I understand it's not sufficient for a real quote, but I was just looking into ballparks here.