4 ms·
We've made the assumption that users will enter malicious code and designed the security boundaries around that. A malicious user that manages to break out of
by bthornbury 9y ago
We've made the assumption that users will enter malicious code and designed the security boundaries around that.
A malicious user that manages to break out of the container environment will only have access to other instances of their own applications. Stronger security policies exist between users.
- ceejayoz 9y agoI read the concern more as "what do you do to stop someone from cURLing an .iso a million times from someone's S3 account".
- bthornbury 9y agoI'm not too sure what you mean here. In terms of DOS'ing our services, we limit disk space usage per job, and are working on bandwidth limitations (this is a weakness, but for now we'll just ban abusers and work with those with legit needs)
- ceejayoz 9y agoNot DOSing your services, using your services to DOS others. Or things like using stolen credit cards to do Bitcoin mining.
- bthornbury 9y agoEvery services provider will deal with this. We have plans but ultimately won't really know until we're in the thick of it. Our plans though are to limit bandwidth and ban abusers. We'll work with Stripe's Radar platform to reduce the stolen credit card fraud.