SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

IT Security and Auditing

gerek avatar
gerek
19 diapositives · 486 Views · Jul 31, 2012

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.

IT Security and Auditing - slide 1
01 / 19IT Security and Auditing
1 / 17

Télécharger la présentation

IT Security and Auditing
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. IT Securityand Auditing Katie Englebretson Rebecca Cone

  2. Why We Audit Common causes of damage: IT Security Cookbook

  3. What is a threat • Something that affects • Confidentiality • Integrity • Availability of business assets and resources

  4. Risk Assessment

  5. 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.

  6. Auditing Regulations • GAAS • SAS • PCAOB • SEC • Sarbanes Oxley

  7. 3 Steps in an Audit • Planning • Performance • Completion

  8. Planning the Audit • Asset Analysis • Current Policy Analysis • Security Objectives • Threat Analysis

  9. Planning the Audit • Impact Analysis • Risk Analysis • Constraints Analysis • Counter Strategy Analysis

  10. What Are We Looking For? • Existence • Completeness • Ownership • Accuracy

  11. Audit Strategies • Reliance Strategy • Substantive Strategy

  12. 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

  13. Auditing Complex Clients • Test Data Approach • Integrated Test Facility • Parallel Simulation • Continuous Auditing *All IT systems have similar functions

  14. 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.

  15. 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.

  16. Parallel System Procedure- Run real data through a simulated “fake” system Problem- difficult to prepare, but don’t have to back out data

  17. Completion • Wrap up loose ends • Examine company as a whole • Compliance • Issue reports

  18. Continuous Auditing • Periodically • After upgrades and patches • After installation of new hardware

  19. www.dilbert.com