{"id":7961,"date":"2022-04-08T16:14:43","date_gmt":"2022-04-08T14:14:43","guid":{"rendered":"https:\/\/www.bayoosoft.com\/?p=7961"},"modified":"2026-02-23T16:19:28","modified_gmt":"2026-02-23T15:19:28","slug":"need-to-know-vs-scattergun-approach-the-right-choice-for-authorization-management","status":"publish","type":"post","link":"https:\/\/www.bayoosoft.com\/en\/bayoosoft-access-manager-en\/need-to-know-vs-scattergun-approach-the-right-choice-for-authorization-management\/","title":{"rendered":"Need-to-know vs. watering can principle: the right choice for authorization management"},"content":{"rendered":"

Need-to-know vs. watering can principle: Why the choice of authorization concept determines security and efficiency<\/h1><\/h1><\/div><\/div><\/div>

Who is allowed to access which data? This question sounds simple, but in practice it is one of the biggest challenges for IT managers. After all, authorization management is not a one-off task: employees change departments, new colleagues start, others leave. Every change entails adjustments to file servers, SharePoint, Active Directory and third-party systems.<\/p>\n

How companies go about this has far-reaching consequences for data security, compliance and the workload of IT administration.<\/p>\n<\/div><\/div><\/div>

<\/span><\/div><\/div><\/div>

The watering can principle: fast, but risky<\/h2><\/h2><\/div>

In many companies, out of necessity, a practice has become established that can be aptly described as the watering can principle: Authorizations are granted generously and across the board, often at departmental level or based on peers with similar job profiles.<\/p>\n

That sounds pragmatic. And it does indeed save time in the short term. But the consequences are serious:<\/p>\n