Hello, data "guardian" here! Being the lonely DBA, I'm pretty much bored with this kind of stuff every day at work, managing nearly 2k databases ranging from simple q&a to financial to "top secret" data. Everything CAN be managed (various degrees of "complications"), but please note that there are SEVERAL variables in this "game". First and foremost (I know, it's silly but there are places where this key piece is missing), a "person accountable for" must be chosen. If that person is yourself, I'd urge to document: - what happens if data is lost - what happens if data is tampered - what happens if data is stolen First two are easy to solve: a proper backup scheme! Third is a real PITA, and must be considered individually.
If you can't trust frontend developers (sadly, you're not the only one), there's the most and effective way for sleeping like a baby every night: they shouldn't deal with data from the production environment anyways to create a frontend, so you create a dev env with sensitive data obscured, it's a simple process ^___^' If you can't trust the backend developers, you're screwed anyways, unless you segregate permissions AND document them (e.g. bob requested access to table x for doing report y). Segregation (always in various degrees of "complications") can also be accompanied by a fixed timeframe where those credentials are valid (i.e. rotation). Given though you're expressing a world where an API exists, you don't have backend developers at all. Trust this though: if you're the "gatekeeper" of the data and YOU have the (legal?!) responsibility, you need to carefully document each and every access you provide to people using that data. If you're not the "gatekeeper" of the data but merely of the "windows" the data is seen/managed from, forcing everyone through an API is the best way to be able to audit (the "gatekeeper" of the data could/SHOULD request you the audit if something happens) On Friday, July 29, 2016 at 6:46:50 PM UTC+2, Alex Glaros wrote: > > agreed Massimo > > my friend who made the suggestion gave me a few more details: For multiple > programmer teams, he gives HTML developers access to the API only, in order > to limit number of programmers writing code that access the database. > > thanks, > > Alex > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
