Defining Accounts and Permissions

Mark Conway Munro · Apress eBooks · 2021

In this modern age of global network connectivity, the need to secure a database should be glaringly obvious. News stories about data breaches, leaked information, and malicious exploitation by hackers provide us a sobering warning about the dangers of unsecured data. As important as it is to stop unauthorized access by outsiders, security permission is a far more complex subject. Even authorized users require restrictions on their activity inside the database. Limitations on the content they can create, view, modify, and use are important to consider. Also, restricting access to the structural design of a database can help stop careless or malicious alternations to the schema, interface, and script functions. Even a minor accidental change to a formula or script can be catastrophic to a company’s workflow and may result in severe financial consequences. Only users with adequate technical skill and knowledge of business logistics should be authorized to act as a developer. This chapter explores the available credentialing features.

Read the paper · More papers on PaperTik