3 ms·
I have always assumed this is about the editing of choices - there is a vast world of OSS choices. And I cannot keep up. I would happily buy Matasano-branded
by lifeisstillgood 14y ago
I have always assumed this is about the editing of choices - there is a vast world of OSS choices. And I cannot keep up.
I would happily buy Matasano-branded cloud servers that talked the AWS/OpenStack API (ie were actually run there) but were imaged off one baseline that was Thomas-Approved.
I dont trust other people's Chef or Puppet recipies to install nginx for me. I would trust yours.
That means I would start writing my application on your branded stack. If that means I get to only use vi on OpenBSD then - hey there is real badge value in it still:-)
And if actually I can only deploy my code to your secure server via a CI process, all the better.
After that we can talk appsec, and scaling.
- danielweber 14y agoThere was a guy in the Pinboard Prosperity Cloud who was working on best-in-class secure VMs. I haven't seen a follow-up but it's only been several weeks. http://static.pinboard.in/prosperity_cloud.htm http://static.pinboard.in/prosperity_cloud.htm
- lifeisstillgood 14y agoThank you - I write six paragraphs to describe your six words - "best-in-class secure VMs". That's what I meant - what he said.:-)
- tptacek 14y agoShit I owe that guy $55.
- jiggy2011 14y agoHaving a secure baseline setup is obviously important. However the point that tptacek seems to be making is that most of the security risk of startups comes from the custom code that they write. You can have the most hardened openBSD setup in the world but if you write a web app that runs shell commands based on user input and you don't validate well enough you might be in for a bad time.
- lifeisstillgood 14y agoIs that really the cause of most security penetrations? Would love to hear from security researchers on this. My guess is a known vulnerability in a third party server is far far more likely to get you compromised (think Wordpress) Than unsantised SQL because one can scan and attack Wordpress automatically but need to manually craft an attack against my specific app Anyway. It's not really how to make startups less vulnerable, it's how to sell tptaceks expertise at a greater scale. If there is overlap good
- jiggy2011 14y agoProbably true, but you don't need to hire Matasano to tell you to patch your Wordpress. If you follow reasonable security practices then the low end automated scanning attacks tend to go away. Security of custom code is really another vector altogether and an expensive one that suddenly becomes important when your stuff gets popular enough to warrant bespoke attacks. I guess the problem startups may have is that they have lots of users (therefor lots of incentive to attack) before they necessarily have the spare change to pay for professional audits of their custom code.
- tptacek 14y agoThey are both major causes of intrusions, but if I was running a SaaS shop, I'd be more worried about vulnerabilities in my own code than I would about vulnerabilities in my operating system. Modulo: don't run Wordpress.
- lifeisstillgood 14y agoWith my developer hat on, it's not so much my code as it is the poor choices frameworks and similar "everyone does it this way" tilutorials make. It's too easy to follow the tutorial and have a default of stuffing everything into a cookie, overly complex orm s and oh you know the rest - and that's before I have written my facebookforfish code I am not sure where that problem fits in - but it feels like the same issue as we urging the OS or securing my postfix. The layer beneath my code is one I want to be secure and be simple. Help with that and I will use your layer choices. That may or may not be profitable.