3 ms·
two of our competitors have poor practice around endpoints that have opened their entire user database. What should we do?
by jacob_rezi 4y ago
two of our competitors have poor practice around endpoints that have opened their entire user database. What should we do?
- akiselev 4y agoTalk to your lawyers.
- greggsy 4y agoCYA by making sure you’re not making the same mistakes. Don’t try to be clever by exposing them. Tell your clients that you apply best (/better) practice.
- yourapostasy 4y agoThese are called kill points in sales. For this kind of kill point however, you better make sure not just your own endpoints have cleanly passed scrutiny, but your entire modeling and process around them doesn’t produce insecure endpoints. Otherwise it is best not to let your sales team use such a kill point.
- jjice 4y agoTangential, but I always wondered why people don't have a separate class/struct/whatever that's actually used to send out. Might be overkill, but having a separate model to represent incoming request, out going requests, and the actual domain model makes me feel a bit more secure as to what's being sent out. It requires more work to update (adding fields to the outgoing models), but gives a bit of piece of mind.
- deleted 4y ago[deleted]
- bcrosby95 4y agoWe do this where I work. It's a lot of extra data types, but they're all extremely simple and better safe than sorry. As a rule, we don't send or receive actual domain objects in our APIs. It doesn't matter if they're currently "safe" - they might not be in the future.