Audit of it infrastructure

14,758 views

Published on

Audit of it infrastructure

Published in: Technology
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
14,758
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
1,094
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide
  • Interception- The data that are transmitted over the network pass through some medium. These data could be intercepted and subject to disclosure. Availability - As networks proliferate, more and more users are remote and access their applications over the network. If network connectivity fails there would be serious interruption to business and consequent damages. Access - Network provides the feasibility for access to the system from anywhere. A single weak point in the network can make all the information assets in the network vulnerable to intruders.
  • Audit of it infrastructure

    1. 1. Audit of IT infrastructure Hardware, Network and Telecommunications Devices
    2. 2. What is IT Audit <ul><li>Examination of the controls within an Information technology (IT) infrastructure. </li></ul><ul><li>Process of collecting and evaluating evidence of an organization's IT infrastructure. </li></ul><ul><li>Understanding and evaluating each control. </li></ul><ul><li>Assess compliance. </li></ul><ul><li>Substantiate the risk of controls not being met. </li></ul>
    3. 3. Why IT Audit? <ul><li>Ensuring servers to be properly configured for both efficiency and security. </li></ul><ul><li>Looking for hardware specific productivity drains. </li></ul><ul><li>Obtain an asset listing of all hardware. </li></ul><ul><li>L ooking for causes of frequent problems. </li></ul><ul><li>E nsuring backup systems are adequate, monitored, tested regularly. </li></ul><ul><li>Determining risks to information assets. </li></ul><ul><li>Assessing controls in order to reduce or mitigate these risks. </li></ul>
    4. 4. Objectives of IT Audit? <ul><li>Continuity (consistent reliability and availability of system -- back-up and ability to recover) </li></ul><ul><li>Management and Maintenance (additions, change procedures, upgrades, and documentation) </li></ul><ul><li>Security (appropriate physical and logical access to network devices and hosts) </li></ul>
    5. 5. Perspectives of IS Audit
    6. 6. ISACA - CobiT <ul><li>Generally applicable and accepted international standard for good practices for IT controls </li></ul><ul><li>based on ISACA ’s existing Control Objectives </li></ul><ul><li>three specific audiences </li></ul><ul><ul><ul><li>management, </li></ul></ul></ul><ul><ul><ul><li>users, and </li></ul></ul></ul><ul><ul><ul><li>auditors. </li></ul></ul></ul>
    7. 7. ISACA - CobiT <ul><li>provides detailed Audit Guidelines for auditors to follow in performing information systems audits </li></ul><ul><li>Audit Guidelines provide a complementary tool to enable the easy application of the Framework and Control Objectives within audit activities </li></ul><ul><li>objectives of auditing </li></ul><ul><ul><ul><li>provide management with reasonable assurance that control objectives are being met </li></ul></ul></ul><ul><ul><ul><li>where there are significant control weaknesses, to substantiate the resulting risks </li></ul></ul></ul><ul><ul><ul><li>Advise management on corrective actions needed </li></ul></ul></ul>
    8. 8. ISO:IEC 27001 2005 <ul><li>International Organisation for Standardization </li></ul><ul><li>International Electrotechnical Commission </li></ul><ul><li>Provided a model for </li></ul><ul><ul><ul><li>Establishing </li></ul></ul></ul><ul><ul><ul><li>Implementing </li></ul></ul></ul><ul><ul><ul><li>Operating </li></ul></ul></ul><ul><ul><ul><li>Monitoring </li></ul></ul></ul><ul><ul><ul><li>Reviewing and </li></ul></ul></ul><ul><ul><ul><li>Improving </li></ul></ul></ul><ul><ul><li>Information Security Management System </li></ul></ul>
    9. 9. ISO:IEC 27001 2005 <ul><li>PDCA model </li></ul><ul><ul><li>Plan  Establish ISMS </li></ul></ul><ul><ul><li>Do  Implement and Operate </li></ul></ul><ul><ul><li>Check  Monitor and Review </li></ul></ul><ul><ul><li>Act  Maintain and improve </li></ul></ul>
    10. 10. ISO:IEC 27001 2005 <ul><li>Control Objectives </li></ul><ul><ul><li>Control </li></ul></ul><ul><ul><ul><li>The policies, procedures, practices and organisational structures designed to provide reasonable assurance that business objectives will be achieved and undesired events will be prevented or detected and corrected </li></ul></ul></ul><ul><ul><li>Control Objective </li></ul></ul><ul><ul><ul><li>A statement of the desired result or purpose to be achieved by implementing control practices in a particular IT activity </li></ul></ul></ul>
    11. 11. ISO:IEC 27001 2005 Control The information security policy is being reviewed at planned intervals or if significant changes occur to ensure its continuing suitability, adequacy, and effectiveness. Review of the information security policy A.5.1.2 Control An information security policy document has been approved by management, and published and communicated to all employees and relevant external parties. The latest version of this document is available for all employees on the ABC Company’s internal network. Information security policy document A.5.1.1 A.5.1 Information security policy Objective: To provide management direction and support for information security in accordance with business requirements and relevant laws and regulations. A.5 Security policy
    12. 12. ISO:IEC 27001 2005 Control Rules for the acceptable use of information and assets associated with information processing facilities are identified, documented, and implemented. Acceptable use of assets A.7.1.3 Control All information and assets associated with information processing facilities are ‘owned’ by a designated part of the organization. Ownership of assets A.7.1.2 Control All assets are clearly identified and an inventory of all-important assets drawn up and maintained. The Classification of Assets is as per the guidelines laid out in Procedure on Risk Assessment. Rules of classification take asset value and importance into account. A list of assets including the owner and relevant details is kept with the respective functional departments. Additional asset details are maintained by the Admin Department for the purposes of audit and keeping track of assets. Inventory of assets A.7.1.1 A.7.1 Responsibility for assets Objective: To achieve and maintain appropriate protection of organizational assets. A.7 Asset management
    13. 13. Information Systems Hardware Infrastructure
    14. 14. Auditing Hardware <ul><li>Hardware asset listing (for your accounting/budgeting and equipment lifecycle planning). </li></ul><ul><li>Analysis of Environmental conditions for equipment including heat and power protection. </li></ul><ul><li>Network design analysis and network diagram (improves support response times with your IT provider). </li></ul><ul><li>Report on appropriateness of hardware in all PC-based equipment (and how that impacts performance). </li></ul>
    15. 15. Auditing Hardware <ul><li>Report on server hardware appropriateness, performance, levels of redundancy (and any associated risks). </li></ul><ul><li>Analysis of Server configuration (and any areas not done properly and if/why they are important). </li></ul><ul><li>Security Analysis on multiple levels. </li></ul><ul><li>Backup systems hardware, software, data sets, disaster readiness and risks. </li></ul>
    16. 16. ISO:IEC 27001 2005 Control Equipment are correctly maintained to ensure its continued availability and integrity. Equipment maintenance A.9.2.4 Control Power and telecommunications cabling carrying data or supporting information services are protected from interception or damage. Cabling security A.9.2.3 Control Security features, service levels, and management requirements of all network services are identified and included in any network services agreement, whether these services are provided in-house or outsourced. Security of network services A.10.6.2 Control Networks are adequately managed and controlled, in order to be protected from threats, and to maintain security for the systems and applications using the network, including information in transit. Network controls A.10.6.1 A.10.6 Network security management Objective: To ensure the protection of information in networks and the protection of the supporting infrastructure.
    17. 17. Routing controls are implemented for networks to ensure that computer connections and information flows do not breach the access control policy of the business applications. Network routing control A.11.4.7 For shared networks, especially those extending across the organization’s boundaries, the capability of users to connect to the network shall be restricted, in line with the access control policy and requirements of the business applications Network connection control A.11.4.6 Groups of information services, users, and information systems are segregated on networks. Segregation in networks A.11.4.5 Physical and logical access to diagnostic and configuration ports shall be controlled. Remote diagnostic and configuration port protection A.11.4.4 Automatic equipment identification is considered as a means to authenticate connections from specific locations and equipment. Equipment identification in the network A.11.4.3 Appropriate authentication methods shall be used to control access by remote users. User authentication for external connections A.11.4.2 Users shall only be provided with access to the services that they have been specifically authorized to use. Policy on use of network services A.11.4.1 A.11.4 Network access control Objective: To prevent unauthorized access to networked services.
    18. 18. Information Systems Network & Telecommunication Infrastructure
    19. 19. Auditing Networks
    20. 20. Network Vulnerabilities & Controls
    21. 21. Auditing Networks <ul><li>Review network policies and procedures </li></ul><ul><li>Review network diagrams (layer 1 & 2), design, and walk-through, list of network equipment and IP address list </li></ul><ul><li>Verify diagrams with Ping and Trace Route </li></ul><ul><li>Review utilization, trouble reports & helpdesk procedures </li></ul>
    22. 22. Auditing Networks <ul><li>Probe systems (Netscan tools and Portscanner) </li></ul><ul><li>Interview network vendors, users, and network technicians </li></ul><ul><li>Review software settings on network equipment </li></ul><ul><li>Inspect computer room and network locations </li></ul><ul><li>Evaluate back-up and operational procedures </li></ul><ul><li>Identify the paths and equipment used to navigate the network </li></ul><ul><li>Identify TCP/IP infrastructure areas of concern </li></ul>
    23. 23. Auditing Networks <ul><li>Break into manageable pieces </li></ul><ul><li>Every network is different and the components and risks must be fully understood </li></ul><ul><li>Identify risks and prioritize </li></ul><ul><li>Dedicate more upfront planning </li></ul><ul><li>RELAX !! It’s not that bad ! </li></ul>
    24. 24. Routers <ul><li>Inappropriate addresses or dangerous protocols accessing hosts/servers </li></ul><ul><li>Inappropriate addresses conducting router maintenance </li></ul><ul><li>Unauthenticated or trusted services used for maintenance </li></ul><ul><li>Damaged router/network device configuration </li></ul>
    25. 25. Routers <ul><li>Failed upgrades or changes </li></ul><ul><li>Not capturing network events </li></ul><ul><li>Default passwords and clear text passwords transmitted over the network </li></ul><ul><li>No console password </li></ul>
    26. 26. Firewalls <ul><li>Network Address Translation </li></ul><ul><li>Intrusion Detection Systems (IDS) </li></ul><ul><li>Virtual Private Networks (VPN) </li></ul><ul><li>Demilitarised Zone (DMZ) </li></ul><ul><li>Proxy Server </li></ul>
    27. 27. Firewalls <ul><li>Obtain Firewall Security policy </li></ul><ul><li>Identify the services </li></ul><ul><li>Identify logging procedure </li></ul><ul><li>Identify configuration management process </li></ul>
    28. 28. Firewall <ul><li>Review </li></ul><ul><ul><ul><li>Authentication controls </li></ul></ul></ul><ul><ul><ul><li>DMZ </li></ul></ul></ul><ul><ul><ul><li>Procedure for Device administration </li></ul></ul></ul><ul><ul><ul><li>Procedure to review the logs </li></ul></ul></ul><ul><ul><ul><li>Risk Management procedure </li></ul></ul></ul><ul><ul><ul><li>Physical access control to firewall </li></ul></ul></ul>
    29. 29. Telecommunication Audit
    30. 30. Telecommunication Audit <ul><li>Assessment of an organization’s telecommunication environment. </li></ul><ul><li>Telecom Audit defines the act of conducting a review, examination and reconciliation of </li></ul><ul><ul><li>Telecom </li></ul></ul><ul><ul><li>Wireless </li></ul></ul><ul><ul><li>Network customer service records </li></ul></ul><ul><ul><li>Invoicing </li></ul></ul><ul><ul><li>Contract agreements </li></ul></ul><ul><ul><li>in order to ensure the accuracy of budgetary forecasting. </li></ul></ul>
    31. 31. Telecommunication Audit <ul><li>Communications equipment such as </li></ul><ul><li>PBX's </li></ul><ul><li>Voice mail systems </li></ul><ul><li>IVRs </li></ul><ul><li>Telephone lines </li></ul><ul><li>Leased lines </li></ul><ul><li>are assessed to determine if they meet current business requirements and if possible alternate solutions should be considered. </li></ul>

    ×