Furthermore, where concerns exist that the aggregation of separate pieces of content from within a database could
lead to an adversary determining more sensitive or classified content, the need-to-know principle can be enforced
through the use of minimum privileges, database views and database roles. Alternatively, the content of concern could
be separated by implementing multiple databases, each with restricted data sets.
Security Control: ISM-0393; Revision: 8; Updated: Jun-21; Applicability: All; Essential Eight: N/A
Databases and their contents are classified based on the sensitivity or classification of data that they contain.
Security Control: ISM-1255; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Database users’ ability to access, insert, modify and remove database contents is restricted based on their work duties.
Security Control: ISM-1268; Revision: 1; Updated: Sep-18; Applicability: All; Essential Eight: N/A
The need-to-know principle is enforced for database contents through the application of minimum privileges, database
views and database roles.
Separation of development, testing and production databases
Using database contents from production environments in development or testing environments could result in
inadequate protection being applied to the database contents.
Security Control: ISM-1274; Revision: 6; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Database contents from production environments are not used in development or testing environments unless the
environment is secured to the same level as the production environment.
Web application interaction with databases
SQL injection attacks are a significant threat to the confidentiality, integrity and availability of database contents.
Specifically, SQL injection attacks can allow an adversary to steal database contents, modify database contents, delete
an entire database or even in some circumstances gain control of the underlying database server. Furthermore, when
database queries from web applications fail they may display detailed error information about the structure of
databases. This can be used by an adversary to further tailor SQL injection attacks.
Security Control: ISM-1275; Revision: 1; Updated: Sep-18; Applicability: All; Essential Eight: N/A
All queries to databases from web applications are filtered for legitimate content and correct syntax.
Security Control: ISM-1276; Revision: 2; Updated: Sep-18; Applicability: All; Essential Eight: N/A
Parameterised queries or stored procedures are used for database interaction instead of dynamically generated queries.
Security Control: ISM-1278; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Web applications are designed to provide as little error information as possible about the structure of databases.
Database event logging
Certain database events can assist in monitoring the security posture of databases, detecting malicious behaviour and
contributing to investigations following cyber security incidents. In doing so, database event logs should be centrally
stored and protected from unauthorised modification and deletion, monitored for signs of compromise, and actioned
when cyber security events are detected.
Security Control: ISM-1537; Revision: 2; Updated: Mar-22; Applicability: All; Essential Eight: N/A
The following events are logged for databases:
access or modification of particularly important content
addition of new users, especially privileged users
changes to user roles or database permissions
attempts to elevate privileges
108
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents