220 likes | 452 Views
IT Security and Auditing. Katie Englebretson Rebecca Cone. Why We Audit. Common causes of damage:. IT Security Cookbook. What is a threat. Something that affects Confidentiality Integrity Availability of business assets and resources. Risk Assessment. Auditing IT.
E N D
IT Securityand Auditing Katie Englebretson Rebecca Cone
Why We Audit Common causes of damage: IT Security Cookbook
What is a threat • Something that affects • Confidentiality • Integrity • Availability of business assets and resources
Auditing IT Clients response to risk = Internal Controls Control Risk = The risk that material misstatements that could occur in an account are not prevented or detected by internal controls.
Auditing Regulations • GAAS • SAS • PCAOB • SEC • Sarbanes Oxley
3 Steps in an Audit • Planning • Performance • Completion
Planning the Audit • Asset Analysis • Current Policy Analysis • Security Objectives • Threat Analysis
Planning the Audit • Impact Analysis • Risk Analysis • Constraints Analysis • Counter Strategy Analysis
What Are We Looking For? • Existence • Completeness • Ownership • Accuracy
Audit Strategies • Reliance Strategy • Substantive Strategy
Determine the Complexity of the Client • Low • Simple, no/few controls • Medium • More advanced, controls exist but still have an audit trail • Most clients are here • High • Very complex, multiple mainframes and extensive databases
Auditing Complex Clients • Test Data Approach • Integrated Test Facility • Parallel Simulation • Continuous Auditing *All IT systems have similar functions
Test Data Approach Procedure-develops simulated “fake” (both good and bad) data and test transaction by running the fake data through the system after hours. Problem- time consuming and it is uncertain if it is really the client’s system because the data is being ran after hours. Also, if the data goes in, it must come out and that can be difficult.
Integrated Test Facility Procedure- develops simulated “fake” (both good and bad) data and test transaction by running the fake data through the system during normal business hours. Problem- time consuming and if the data goes in, it must come out and that can be difficult.
Parallel System Procedure- Run real data through a simulated “fake” system Problem- difficult to prepare, but don’t have to back out data
Completion • Wrap up loose ends • Examine company as a whole • Compliance • Issue reports
Continuous Auditing • Periodically • After upgrades and patches • After installation of new hardware