18.12.2012 Views

Proceedings

Proceedings

Proceedings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• Export files<br />

The auditor should check for the existence of the export file. Attackers might<br />

either export the database’s data including users’ passwords or be able to read a<br />

legitimate export which could facilitate the database attack.<br />

• Archive log files<br />

The data usually archived in the log files are precious and should be protected.<br />

The auditor should locate the archive log files and check that no user except the<br />

legitimate ones can read them.<br />

• Access to native PL/SQL compiler in production environment<br />

The access to native PL/SQL compilation in production should be removed. The<br />

access to this functionality would allow the execution of other binary files and to<br />

wrap existing packages with the attackers’ own code.<br />

• Vulnerability scan<br />

The auditor should review the OS vulnerabilities scan report.<br />

Oracle database audit tests<br />

During the fieldwork, the auditor will test the database implemented controls. Listed<br />

below are the critical audit tests that should be performed:<br />

• Oracle database support<br />

The auditor should check if the database version running on the servers is<br />

currently supported by the vendor and if not, to look for additional agreements<br />

between organization and vendor.<br />

• Patch management process<br />

The auditor should assess the process for reviewing and applying databases and<br />

operating system patches. The entire patch management process and the respective<br />

procedures should be checked. Evidence must be provided related to a sample of<br />

patches chosen by the auditor.<br />

• Promotion to production process<br />

All promotions to production (patches, updates, new functionalities, bug fixes)<br />

should be thoroughly tested before bringing them into production environment. A<br />

severe control process must be in place for promotion to production activities.<br />

• Database change control process<br />

The auditor should review the change control process to ensure that all database<br />

changes are performed in a controlled manner. Evidence for a sample of recent<br />

database changes should be obtained and analysed.<br />

• Incident management process<br />

The auditor should review the incident management process. All incidents must be<br />

recorded in a history log and reports on the respective incidents must exist. In a<br />

later stage of the organization’s maturity level, all the solutions used for solving<br />

incidents could be gathered to organize a knowledge database. A sample of<br />

database incidents should be reviewed.<br />

~ 297 ~

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!