Controlling Auditing: and The SDLC
Controlling Auditing: and The SDLC
User must be actively involved in the systems development process. The user can and should provide a detailed written description of the logical needs that must be satisfied by the system. The creation of a user specification document often involves the joint efforts of the user and system professional.
Technical
Design Activities
The technical design activities translate the user specification into set of detailed technical specification of a system that meets the user needs.
Internal Audit
Participation
The internal Auditor can serve as a liaison between users and the system
Verify that SDLC are applied consistently and in accordance with managements policies. Determine that the system as originally implemented was free from material errors and fraud. Confirm that the system was judged to be necessary and justified at various checkpoints throughout the SDLC. Verify that the system documentation is sufficiently accurate to facilitate audit and maintenance activities.
User and computer services management properly authorized the project. A preliminary feasibility study showed that the project has merit. A detailed analysis of user needs was conducted that resulted in alternative general designs. A cost-benefit analysis was conducted using reasonably accurate figures. The projects documentation shows that the detailed design was an appropriate and accurate solution to the users problem. Test results show that the system was thoroughly tested at both the individual module and the total system level before implementation. There is a checklist of specific problems detected during the conversion period, along with evidence that they were corrected in the maintenance phase. Systems documentation complies with organizational requirements and standards .
Controlling System Maintenance Maintenance Authorization, Testing and Documentation Source Program Library Controls The Worst-Case Situation: No Controls A Controlled SPL Environment
Password Control Separate Test Libraries Audit Trail and Management Reports Program Version Numbers Controlling Access to Maintenance Commands
Audit Objective Related to system Maintenance Maintenance procedures protect applications from unauthorized changes Application are free from material errors Program libraries are protected from unauthorized access
.
System Development Programmers
Source Program
Compiler Program
Object Module
Production Application
Figure 5.13 Source Program Library under the Control of SPL Management Software
05
Application Program
05
Maintenance Request
#5 Program
Auditor Confirms Maintenance request with user management to verify maintenance authorization and content
Listing
05
Auditor reconciles program maintenance request, program listings and accuracy of program maintenance
Audit Procedure Related to System Maintenance Identify Unauthorized Changes Reconcile program version number Confirm maintenance authorization Identify Application Errors Reconcile the source code Review test results Retest the Program
Test Access to Libraries Review Programmer authority tables Test Authority tabe