As a database admin of the GCNotify ecosystem,
I want each user to have their own database login,
So that I can isolate risk and auditing for developers accesses.
As a GCNotify stakeholder,
I want each user to have their own database login,
So that I can reduce security and access risk,
And align with the organizational security practices.
WHY are we building?
To isolate the database logins from applications to developers. We can then build different auditing patterns and permissions for each of these with proper automatic monitoring.
WHAT are we building?
Separate database logins for each developer.
Separate application logins from developers access (a developer should not use an application login that is used for gcnotify-admin for example).
Have monitoring in place to check if developers use the application logins and raise a warning if that happens.
VALUE created by our solution
Better alignment with organization's best practices.
Better security.
Better auditing.
Acceptance Criteria
Given a developer needs to run queries on the production database, then they use their own isolated database login.
[ ] A warning alert is in place if a developer uses an application database logins.
[ ] Auditing for developer's database logins is tailored for their usage and forwarded to sentinel.
[ ] One login per developer is available and leverages IAM roles.
[ ] A mechanism to add and remove developers' login is implemented and documented.
Description
As a database admin of the GCNotify ecosystem, I want each user to have their own database login, So that I can isolate risk and auditing for developers accesses.
As a GCNotify stakeholder, I want each user to have their own database login, So that I can reduce security and access risk, And align with the organizational security practices.
WHY are we building?
To isolate the database logins from applications to developers. We can then build different auditing patterns and permissions for each of these with proper automatic monitoring.
WHAT are we building?
VALUE created by our solution
Acceptance Criteria
Given a developer needs to run queries on the production database, then they use their own isolated database login.
QA Steps