...
| Technique | Description | Benefits |
|---|---|---|
| Macro Security for Confluence | Content using SQL macros can only be created or updated by trusted users while still allowing other users the ability to view the content. This is implemented by the Confluence administrator installing CMSP using UPM and configuring access. |
|
| Database permissions | Database permissions for the user configured for the SQL data source can be restricted. For instance, view only authority. This is recommended when only subset of access is needed, especially for browse only. |
|
| Allow only SQL Query macro | Some databases (like PostgreSQL) enforce a JDBC remote access mode for read-only. The sql-query macro uses this support. This can be implemented by having the Confluence administrator disable the other sql macros in the UPM. | Restrict access to query only. |
| Allow only SQL File macro | The sql-file macro only runs Confluence administrator controlled SQL. This can be implemented by having the Confluence administrator disable the other sql macros in the UPM. See Run SQL queries securely, without page edit restrictions. | Only pre-defined SQL can be run. |
| Role based security | Use database role security to control what data is available. | Data shown based on user id and role. |
| Use parameter markers | Prevent SQL injection attacks by using parameter markers. This in only necessary when the SQL statements are partially constructed from user input - for example, using the RUN. See Wikipedia: SQL injection. Parameter markers are supported by SQL for Confluence. | Prevent SQL injection attacks when users are allowed to provide statement construction input. |
...