Design of a priori threat prevention embedded in in-house application / Faiqah Hafidzah Halim
As application grow in size, complexity, and heterogeneity in response to growing computational needs, it is increasingly difficult to build a system that satisfies all requirements and design constraints that it will encounter during its lifetime. Furthermore, many of these systems are required to...
Saved in:
| Main Author: | |
|---|---|
| Format: | Thesis |
| Language: | English |
| Published: |
2014
|
| Online Access: | https://ir.uitm.edu.my/id/eprint/16268/1/16268.pdf https://ir.uitm.edu.my/id/eprint/16268/ |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Summary: | As application grow in size, complexity, and heterogeneity in response to growing computational needs, it is increasingly difficult to build a system that satisfies all requirements and design constraints that it will encounter during its lifetime. Furthermore, many of these systems are required to run continuously, disallowing downtimes while code is modified. As a result, it is important for an application to adapt in response to new requirements and environmental conditions after it has been deployed. Due to their high complexity, adaptive and autonomic systems are generally difficult to specify, design, verify and validate. Embedded Audit Module (EAM) is modules code built into application programs that are designed to capture audit-related information on an ongoing basis. EAM provides the ability to capture data changes within a system. The implementation of the audit module in in-house developed information system can lift the burden from IT auditor and database administrator in managing the sensitive data and to track and monitor any unauthorized database transaction. This study, therefore, offers an attempt to design a priori threat prevention embedded in in-house application system. In order to achieve the aim of this research, the verified requirements for Embedded Audit Module were generalized. Lastly, the design of EAM was proposed. The processes involved were identifying and planning the research, data collection and lastly design the EAM according to the requirements captured. This research has produced the Software Design Document to communicate the design of EAM. The design of EAM produced can be used in order to lessen the threat towards the in house developed information system and reduce the work to be done by IT Auditor and DBA. |
|---|