2 ms·
It's security in depth in this case, as I recall. There are subtleties in how you confirm or deny the existence of a record and for their particular solution to
by hinkley 4y ago
It's security in depth in this case, as I recall. There are subtleties in how you confirm or deny the existence of a record and for their particular solution to the problem you would get a 403 vs a 404 for a record you did not have access to.
Knowing how much activity a competitor is adding into a project management system isn't a lot of data, but it's more than zero.
- avianlyric 4y agoThere’s a simple solution to that. Always return 403, it’s what you should be doing regardless of your underlying data model. You should always be determine right to access a record before attempting to look it up. If you can’t determine ACLs without the lookup, then your permissions layer should always assume the requester doesn’t have permission to view a non-existent record and return a 403. Doing anything else is dangerous, and randomising PKs is a sticky plaster over a badly designed access control system.