Security rules
Security is the protection of your software from unauthorized access, use, or destruction.
7 are general rules (G- codes) and 8 are APEX rules (A- codes). Start with the highest-severity security rules below, or browse the full list.
Most severe security rules
- G-1110 Avoid connect users that own database objects. Blocker
- G-1120 Avoid granting system privileges to connect users. Blocker
- G-1150 Always limit privileges of schema owners according to principle of least privileges. Blocker
- G-7510 Always prefix Oracle supplied packages with owner schema name. Blocker
- G-7515 Always prefix Oracle supplied object types with owner schema name. Blocker
- G-9010 Always use a format model in string to date/time conversion functions. Blocker
- G-9501 Never use parameter in string expression of dynamic SQL. Use asserted local variable instead. Blocker
- A-0700 Always enable Session State Protection at the application level. Blocker
- A-0720 Always enable Page Access Protection. Blocker
- A-0770 Never allow application pages within an HTML frame. Blocker
All 15 security rules
-
G-1110 Avoid connect users that own database objects.Blocker Security
-
G-1120 Avoid granting system privileges to connect users.Blocker Security
-
G-1150 Always limit privileges of schema owners according to principle of least privileges.Blocker Security
-
G-7510 Always prefix Oracle supplied packages with owner schema name.Blocker Security
-
G-7515 Always prefix Oracle supplied object types with owner schema name.Blocker Security
-
G-9010 Always use a format model in string to date/time conversion functions.Blocker Security
-
G-9501 Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.Blocker Security
-
A-0700 Always enable Session State Protection at the application level.Blocker Security
-
A-0720 Always enable Page Access Protection.Blocker Security
-
A-0770 Never allow application pages within an HTML frame.Blocker Security
-
A-1100 New Try to keep hidden page items protected.Blocker Security
-
A-1340 Avoid pages without an authorization scheme.Critical Security
-
A-1410 Never set session lifetime or idle time to 0 (unlimited).Critical Security
-
A-2300 New Never use the HTML (Unsafe) format on Display-Only items.Critical Security
-
A-3080 New Avoid making Interactive Grid columns read-only with CSS only.Blocker Security
15 total
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.
- 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 severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- Rules by tag - Topics such as SQL, performance and naming.
- All rules - Search and filter the complete rule set.