AnsweredAssumed Answered

Best Practices for Defining Security

Question asked by techt on Feb 13, 2019

We have a manufacturing application that we are preparing to roll out to the rest of the company. Beyond the simple - view, edit, delete - security controls, does anyone have any recommendations about how to set up security so that it's manageable and maintainable?


While we could build a grid of every field in every table to manage what level of access any particular privilege set, my experience is that the more involved the security becomes, the harder it is to test and debug, not to mention to maintain. So I'm looking for best practices on how to define a database from a security standpoint that is easier to implement and maintain. Does anyone have a template or other application they use to define and coordinate privilege sets to implement security? Are there any recommendations from others about how to best approach security requirements?