2,860 karma · joined October 12, 2012
Cloud security, tech startups, NYC.
EM, Cloud Security at Stripe. Previously: founder of CloudSploit (cloud security platform), acquired by Aqua Security in 2019.
Security - complexity will absolutely kill you. I know it’s fun to experiment with Kubernetes and multi-region infrastructure deployments, but that does nothing but increase your attack surface. When we were acquired, I had a single static website hosted on AWS S3, one RDS database, and a handful of Lambda functions behind an API Gateway. You still need to follow best practices: use TLS for all connections, encrypt customer data, properly segment application users, OWASP top 10, etc. but that’s much easier to do with a simple application. Minimize application dependencies, scan them for venerabilities using free tools like Snyk, and keep things up to date.
Compliance: Depending on your domain, you may need to get a SOC II report at some point. Don’t do it until you need it, but when you do, just pay a company like Secureframe (full disclosure: I’m an advisor for them, but there are other similar companies).
Single Sign On: we used Auth0, which was great until we reached 10(?) enterprise connectors and it went from free to $15k/yr. We then migrated to AWS Cognito. If I did it again, I’d just use Cognito to begin with, but wouldn’t build the integration until you actually have customers asking for it.
Marketing: my weaker spot. I was a developer, so had a skeptical view of marketing. We tried a lot of things (agencies, paywalled content, contract writers, etc). I’m still convinced that the highest impact marketing was deeply technical content (doesn’t even need to be about the product, just the same problem space) that was published on our blog for free with a link at the bottom to our product. Simple and effective. Reddit ads on niche subreddits were helpful, especially with getting early users. Marketing agencies are probably overkill until you’ve got actual PMF.
Sales: you need to do the selling. Don’t hire a salesperson until you’ve got a significant number of users. “But I won’t have time to develop if I’m selling.” Yes, exactly. And you won’t have anyone buying if you spend all your time developing and not talking to users. It’s critical that you personally talk to every user as much as possible.
Pricing: I made the mistake of underpricing the product for a long time. I thought developers would love the low cost model. In reality, their companies were paying, and, when you give someone a company credit card, they’re a bit more willing to pay more for a good product. You can still price lower than the competition to get users in the door, but don’t try to be the bargain app. Monthly subscriptions are good, annual are better, but bring tougher sales cycles (enterprises will want to negotiate the contract, add their own legal terms, etc).
It’s a bit tough to give much more advice without knowing what domain you’re operating in, but hopefully that was helpful!
Because of this, I approach side projects from the perspective of getting to revenue as quickly as possible, as opposed to, for example, hacking away at something just for fun or learning something new. Those are entirely valid reasons to start side projects, but I personally don't get the same motivation from them and have found myself quickly getting bored.
My personal preference is to focus on SMB/mid-size B2B SaaS with the goal of eventually replacing full-time job income. For me, consumer SaaS is too small - you're making $5-$20/month/user and therefore need 100s or 1000s of users to reach that goal. Enterprise SaaS is too difficult for a side project (sales cycles are too long/complex). Most mid-size companies are willing to pay a few hundred/month for a good service. As an example, if I can charge $300/month, I only need 50 customers to generate the equivalent income of a decent-paying tech job. The challenge, of course, is finding an idea that meets those requirements!
I cannot fathom how easy it is for these sham "award" companies to make money; it seems every security startup has at least 3 or 4 of them plastered on their home pages. But it begs the question: how did CIOReview and similar companies become so popular (or trusted?) to the point where a feature on their website is _worth_ $3000?
That being said, I’ve worked with, and hired folks who had startups that fizzled out and they didn’t seem to feel that they were at a disadvantage. As a hiring manager now, I’d certainly view any founder experience positively (although I’m admittedly biased).
This could lead to a scenario where no one knows what to believe, internal systems are down, attackers are setting up fake IR channels to get even more info, etc. There’s no way most companies could weather an onslaught like that.
[1] https://twitter.com/Savitar0x01/status/1570580235716014081
VCs are constantly scanning GitHub these days to find open source projects and new tools (ones that might evolve into SaaS products or ones that might indicate a trending product area). IMO, you should charge for _that_ type of feature - maybe a weekly newsletter that summarizes all of the trending repos from the past week for a certain keyword.
Is there any way to fight back against this? I've personally experienced getting a bill after a routine office visit with tons of charges I didn't recognize and procedures they absolutely did not perform. In some cases, it equates to $0 after my insurance pays, but in others it results in quite a bit of extra expenses (especially since I'm on a HDHP).
Every product on the site seems to be rated 4.5+, which makes sense if they’re rejecting reviews in this way.
> The AWS account takeover was possible because a highly privileged IAM role had been assigned to the EC2 instance running the vulnerable Docker container app
This attack isn't unique to Log4Shell; it's a symptom of giving your (compromised) EC2 instance global admin access.
The Cloud Security team defines security primitives and guardrails to allow our colleagues to quickly and confidently build for Stripe’s users. Our scope includes cloud security architecture, data-driven definition of security baselines, centralized controls, and strategic direction of security efforts for our cloud environment.
Our team is working on some really interesting and cross-cutting projects! Recently, we've been exploring AWS SCPs to enforce proper service usage across our fleet of accounts, writing detections to flag misconfigured cloud resources, and integrating Terraform scanning tools in our CI/CD pipelines to prevent those misconfigurations in the first place.
We have two roles open: Software Engineer[0] and Staff Engineer. These roles do require software development experience.
Applying: If you're interested, please apply directly via the links below (you can also email me at "fuller" @ [company name] so I can tag your application internally). I'm happy to answer questions via email as well (I am the hiring manager for these roles).
[0] Note: The Software Engineer, Security role is a generalist role in which you'd be considered across multiple teams (including Cloud Security). You can discuss your preferences with the recruiter during the initial call.
Links:
Staff Engineer: https://stripe.com/jobs/listing/staff-engineer-cloud-securit...
Software Engineer: https://stripe.com/jobs/listing/backend-engineer-security-in...
Tags: cloud, security, infrastructure, AWS