Rules tagged with: PinkDB
The Pink Database paradigm (PinkDB) is an application architecture for database-centric applications.
All 5 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
All 5 PinkDB rules
-
G-1110 Avoid connect users that own database objects.Blocker Security
-
G-1120 Avoid granting system privileges to connect users.Blocker Security
-
G-1130 Avoid granting table access to API roles.Critical Maintainability
-
G-1140 Avoid granting object privileges directly to connect users.Minor Maintainability
-
G-1150 Always limit privileges of schema owners according to principle of least privileges.Blocker Security
5 total
Related tags
Tags that appear on the same rules as PinkDB:
- Pattern (5 shared)
More ways to browse rules
- Trivadis PL/SQL & SQL guideline rules - Rules that implement the Trivadis coding guidelines.
- OWASP-related security rules - Rules that name an OWASP Top 10 risk category.
- Oracle APEX rules - Checks for APEX applications, pages, items and regions.
- PostgreSQL rules - Rules that also apply to PostgreSQL and PL/pgSQL.
- Security rules - All rules in the Security quality area.
- Reliability rules - Rules that prevent bugs and failures at run time.
- Maintainability rules - Rules for code that is easy to read and change.
- Rules by quality area - Security, reliability and maintainability.
- Rules by severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- All rules - Search and filter the complete rule set.