CCNA Security - Chapter 9


Published on

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • More Information: The encryption of DVD movies, which uses a weak algorithm called Content Scrambling System (CSS), is an example of bad assumptions made about the scope of system use. The original assumption was that DVD discs would be played only on hardware players, where the decryption keys could be stored in a tamper-resistant chip inside the player, making it extremely hard for even skilled attackers to compromise the DVD discs. However, when software DVD players appeared, the DVD discs were quickly reverse engineered, because making software tamper resistant is next to impossible against a determined attacker. The keys were recovered from one of the well-known players, and an algorithm was published on the Internet, together with the keys. The response strategy of the DVD industry was to try to ban the publishing of the CSS algorithm and keys, but the decision of the court that the CSS algorithm source code was essentially free speech stopped much of their efforts. Another example of a wrong or poor assumption was the lack of encryption of US cellular traffic. When cellular phones were first introduced, the assumption was that scanners, which could intercept cellular traffic, were too expensive to mount any large-scale attacks against call confidentiality in cellular networks. In a couple of years, the price of these scanners dropped to the point that the scanners were available to virtually anyone. Thus, bad assumptions compromised the protection policy of the cellular network. The next-generation U.S. cellular service uses digital transmission, but the same assumption was made, that digital scanners used to intercept traffic are too expensive. As technology advances, the same story has unfolded for the digital transmissions.
  • General Policies AUP : Defines the acceptable use of equipment and computing services, such as email, and the appropriate security measures that employees should take to protect the corporate resources and proprietary information. Account access request policy : Formalizes the account and access request process within the organization. Users and system administrators who bypass the standard processes for account and access requests can cause legal action against the organization. Acquisition assessment policy : Defines the responsibilities regarding corporate acquisitions and defines the minimum requirements that the information security group must complete for an acquisition assessment. Audit policy : Conducts audits and risk assessments to ensure integrity of information and resources, investigates incidents, ensures conformance to security policies, and monitors user and system activity where appropriate. Information sensitivity policy : Defines the requirements for classifying and securing information in a manner appropriate to its sensitivity level. Password policy : Defines the standards for creating, protecting, and changing strong passwords. Risk assessment policy : Defines the requirements and provides the authority for the information security team to identify, assess, and mitigate risks to the information infrastructure that is associated with conducting business. Global web server policy : Defines the standards that are required by all web hosts. Email Policies Automatically forwarded email policy : Defines the rules for enabling automatic forwarding of emails to another account. Generally, this policy restricts automatic e-mail forwarding to an external destination without prior approval from the appropriate manager or director. Email policy : Defines the standards for use of email. Creation, distribution and receipt of SPAM may be covered here as well as in the AUP. Remote Access Policies Dial-in access policy : Defines the appropriate dial-in access and its use by authorized personnel. Remote-access policy : Defines the standards for connecting to the organization network from any host or network external to the organization. Virtual private network (VPN) security policy : Defines the requirements for remote-access IP Security (IPsec) or other VPN connections to the organization network. Telephony Policy Analog and ISDN line policy : Defines the standards to use analog and ISDN lines for sending and receiving faxes and for connection to computers. Application Policies Acceptable encryption policy : Defines the requirements for encryption algorithms that are used within the organization. Application service provider (ASP) policy : Defines the minimum security criteria that an ASP must execute before the organization uses them on a project. Database credentials coding policy : Defines the requirements for securely storing and retrieving database usernames and passwords. Interprocess communications policy : Defines the security requirements that any two or more processes must meet when they communicate with each other using a network socket or operating system socket. For example, requiring the use of HTTPS. Project security policy : Defines requirements for project managers to review all projects for possible security requirements. Source code protection policy : Establishes minimum information security requirements for managing product source code. Network Policies Extranet policy : Defines the requirements of a third-party organization when that organization must access the network. This often includes signing a third-party connection agreement. Minimum requirements for network access policy : Defines the standards and requirements for any device that requires connectivity to the internal network. Network access standards: Defines the standards for secure physical port access for all wired and wireless network data ports. Router and switch security policy : Defines the minimal security configuration standards for routers and switches inside the network or used in a production capacity. Server security policy : Defines the minimal security configuration standards for servers inside the network or used in a production capacity. Wireless Communication Policy Use policy : Defines standards for wireless systems that are used to connect to the network.
  • CCNA Security - Chapter 9

    1. 1. CCNA Security Chapter Nine Managing a Secure Network© 2009 Cisco Learning Institute. 1
    2. 2. Lesson Planning • This lesson should take 3-4 hours to present • The lesson should include lecture, demonstrations, discussions and assessments • The lesson can be taught in person or using remote instruction© 2009 Cisco Learning Institute. 2
    3. 3. Major Concepts • Describe the principles of secure network design. • Describe the Cisco Self Defending Network. • Describe the role of operations security in a network. • Describe the various techniques and tools to use for network security testing. • Describe the principles of business continuity planning and disaster recovery. • Describe the SDLC and how to use it to design a Secure Network Life Cycle management process. • Describe the functions, goals, role, and structure of a comprehensive security policy.© 2009 Cisco Learning Institute. 3
    4. 4. Lesson Objectives Upon completion of this lesson, the successful participant will be able to: 1.Describe the high-level considerations for ensuring that a network is secure. 2.Describe how to identify threats, risks, and consequences of exploited services. 3.Describe the benefits of risk management and the measures to take to optimize risk management. 4.Describe the CSDN and describe the phases, benefits, and collaborative systems of a CSDN. 5.Describe the Cisco Threat Control Solution and the Cisco Secure Communications Solution. 6.Describe the positioning of the Cisco Integrated Security Portfolio.© 2009 Cisco Learning Institute. 4
    5. 5. Lesson Objectives 7. Describe the overarching concepts of operations security. 8. Describe the core principles of operations security. 9. Describe the role of and the techniques used in network security testing. 10. Describe the tools used in network security testing 11. Describe business continuity planning and disaster recovery 12. Describe the degrees of disruption to business operations and the types of backup. 13. Describe the SDLC. 14. Describe the 5 phases of the SDLC 15. Describe the goals of a security policy.© 2009 Cisco Learning Institute. 5
    6. 6. Lesson Objectives 16. Describe the structure of a security policy. 17. Describe the standards, guidelines, and procedures of a security policy. 18. Describe the roles and responsibilities entailed within a security policy. 19. Describe the concepts of security awareness and how to achieve security awareness through education and training. 20. Describe in brief major laws and ethical guidelines for network security. 21. Describe how to respond to a security breach.© 2009 Cisco Learning Institute. 6
    7. 7. Developing Security Policies • Business needs: What does the organization want to do with the network? What are the needs of the organization? • Threat identification: What threats are most likely to occur, given the organization’s purpose and systems? • Risk analysis: What is the cost versus benefit analysis of mitigating, transferring and accepting various security risk? • Security needs: What are the policies, procedures, standards, and guidelines needed to address business needs and risks? • Industry-recommended practices: What are the security practices that similar organizes currently employ? • Security operations: What are the current procedures for system hardening, incident response, monitoring, maintenance, and auditing of the system for compliance?© 2009 Cisco Learning Institute. 7
    8. 8. Risk Management Guidelines • Expect that any aspect of a security system might fail. • Identify any elements that fail-open. Fail-open occurs when a failure results in a complete bypass of the security function. • Try to identify all attack possibilities. • Evaluate the probability of exploitation. The focus should be on the resources that are needed to create an attack. • Assume that people will make mistakes. • Attackers will not use common and well-established techniques to compromise a system. • Check all assumptions with other people. They might have a fresh perspective on potential threats and their probability.© 2009 Cisco Learning Institute. 8
    9. 9. Threat Identification – Bank Scenario Identified Threats Insider attack on the system Internal system compromise Data Center DestructionStolen customer data Phony transactions Data Input errors© 2009 Cisco Learning Institute. 9
    10. 10. Risk Analysis • Evaluate each threat to determine its severity and probability • Quantitative Risk Analysis uses a mathematical model • Qualitative Risk Analysis uses a scenario-based model Qualitative Risk Analysis This is a test – it is only a test of the material that we actually want.. Quantitative Risk Analysis© 2009 Cisco Learning Institute. 10
    11. 11. Quantitative Risk Analysis • Asset Value (AV) is the cost of an individual asset. • Exposure Factor (EF) is the loss, represented as a percentage, that a realized threat could have on an asset. • Single Loss Expectancy (SLE) is the result of AV * EF, or the cost of a single instance of a threat.© 2009 Cisco Learning Institute. 11
    12. 12. Annualized Rate of Occurrence • Annualized Rate of Occurrence (ARO) - estimated frequency that a threat is expected to occur. • Single Loss Expectancy (SLE) • Annualized Loss Expectancy (ALE) - expected financial loss that an individual threat will cause an organization. ALE = SLE *ARO© 2009 Cisco Learning Institute. 12
    13. 13. Ways to Handle Risk • Risk management—Uses the deployment of protection mechanisms to reduce risks to acceptable levels. Risk management is the most basic and the most difficult aspect of building secure systems, because it requires good knowledge of risks, risk environments, and mitigation methods. • Risk avoidance—Eliminates risk by avoiding the threats altogether, which is usually not an option in the commercial world, where controlled (managed) risk enables profits.© 2009 Cisco Learning Institute. 13
    14. 14. Risk Management Scenario • Internal system compromise—Provide the least amount of privilege access possible to the inside, and utilize a secure multi- tiered application which minimizes inside access. • Stolen customer data—Keep all of the customer data on inside servers, and only transfer data to the outside on demand. • Phony transactions if external server is broken into—Allow only man-in-the-middle attacks on the external server and design the external server application so that is does not to allow arbitrary transactions to be called for any customer account. • Phony transactions if customer PIN or smart card is stolen— Use a quick refresh of revocation lists and have a contract with the user which forces the user to assume responsibility for stolen token cards.© 2009 Cisco Learning Institute. 14
    15. 15. Risk Management Scenario • Insider attack on the system—Strictly limit inside access to the application and provide strict auditing of all accesses from the inside. • Data input error—enhance the security of database applications and provide redundant checking system in order to reduce data entry errors • Data Center destruction—Ensure backups are kept off campus and that additional equipment is on-hand. Enhance defenses against flooding by raising equipment and other precautions.© 2009 Cisco Learning Institute. 15
    16. 16. Risk Avoidance Scenario Using the risk avoidance approach, a company would decide not to offer e-banking service at all because it would be deemed too risky.© 2009 Cisco Learning Institute. 16
    17. 17. Introduction to CiscoSelf-Defending Network • Least Privilege Concept • Cisco Self-Defending Network Principles • Cisco Self-Defending Network Defined • Collaborative Systems Enabling Unparalleled Security© 2009 Cisco Learning Institute. 17
    18. 18. Least Privilege Concept Web Server Permit HTTP Only Permit HTTP Only Deny All Internet Inside • Inside and outside users only need access to the web server program on the exposed host. – The web server does not need to open any connections to the inside or outside. – The firewall enforces those minimal permissions.Cisco Networking Academy Storyboard Template © 2009, Cisco Systems, Inc. © 2009 Cisco Learning Institute. 18
    19. 19. Cisco Self-Defending NetworkPrinciples Integrated Collaborative Adaptive Enabling every Collaboration among the Proactive security element to be a point services and devices technologies that of defense and policy throughout automatically prevent enforcement the network to thwart threats attacks© 2009 Cisco Learning Institute. 19
    20. 20. Cisco Self-Defending Network Defined Efficient securitymanagement, control, and Operational Control response and Policy ManagementAdvanced technologiesand security services that:  Mitigate the effects of Threat Control and Secure outbreaks Containment Communications  Protect critical assets  Ensure privacy Security as an Secure Network Platform integral, fundamental network feature© 2009 Cisco Learning Institute. 20
    21. 21. Collaborative Systems EnablingUnparalleled Security • 360º visibility and protection: – Delivering comprehensive Policy Threat Management Management and proactive network defense Cisco Security Cisco Security Manager MARS • Simplified control: – Streamlining policy and threat management across Cisco NAC Appliance Cisco IPS Sensor Software, Cisco IOS Software, and and Cisco Security the network Agent Cisco ASA Adaptive Security Appliances • Business resiliency: Endpoint Network – Ensuring the enterprise Security Infrastructure operations© 2009 Cisco Learning Institute. 21
    22. 22. Cisco Threat Control Solutions • Threat control for endpoints: This element defends against threats most commonly introduced by Internet use, such as viruses, spyware, and other malicious content. • Threat control for infrastructure: This element safeguards the server and application infrastructure against attacks and intrusions. It also defends against internal and external attempts to penetrate or attack servers and information resources through application and operating system vulnerabilities. • Threat control for e-mail: This element protects business productivity, resource availability, and confidential information by stopping e-mail initiated threats.© 2009 Cisco Learning Institute. 22
    23. 23. Secure Communications Benefits to implementing a secure communication structure: • Improve business productivity and efficiency • Enable new business applications • Help comply with information privacy regulations Secure Communications for Remote Access Provides highly secure, customizable access to corporate networks and applications by establishing an encrypted tunnel across the Internet Secure Communications for Site-to-Site Access Provides an Internet-based WAN infrastructure for connecting branch offices, home offices, or the sites of business partners to all or portions of a network© 2009 Cisco Learning Institute. 23
    24. 24. Operational Control andPolicy Management The Cisco Security Management Suite provides a number of benefits: • Increases speed and accuracy of policy deployment • Improves visibility to monitor end-to- end security • Provides more rapid response to threats • Enforces corporate policy compliance • Enhances proper workflow management© 2009 Cisco Learning Institute. 24
    25. 25. Cisco Security Manager • Responds faster to threats by allowing an administrator to define and assign new security policies • Provide flexible methods to manage devices and policies • Contains extensive animated • It integrates with Cisco Security help for the new user MARS to correlate events with • Allows an administrator to the associated firewall rules centrally specify which policies • It provides the ability to assign are shared and inherited specific tasks to each • It integrates with Cisco Secure administrator during the ACS deployment of a policy© 2009 Cisco Learning Institute. 25
    26. 26. Cisco Security MARS • Greatly reduces false positives • Defines the most effective mitigation responses • Promotes awareness of environmental anomalies • Provides quick and easy • Makes precise access to audit recommendations for compliance reports threat removal,© 2009 Cisco Learning Institute. 26
    27. 27. Secure Network PlatformSecurity Services Integrated into the Network Advanced Technologies and Services Automated Threat Virtualized Behavioral-Based Integrate Response Security Services Protection Advanced Endpoint Posture Dynamic DDoS Endpoint and Application- Services Control Mitigation Layer Inspection Security Services Where Needed SSL Integrate Advanced Security Point IPsec and IPS Products VPN Firewall Access Control Network Antivirus Integrated Collaborative Adaptive Leverage IPsec and SSL IPS IP Network Existing VPN Investment Firewall Access Control Network Antivirus© 2009 Cisco Learning Institute. 27
    28. 28. Core Topology MARS ACS VPN Remote Worker Intern Firewall et VPN IPS WAN Iron Port VPN CSARemote Branch LAN Web Email Server Server DNS© 2009 Cisco Learning Institute. 28
    29. 29. Operations Security • Cisco Self-Defending Network design provides products that can deploy independently of one another • All networks will be vulnerable to attack if the planning, implementation, operations, and maintenance of the network do not adhere to operational security practices • Operations security starts with the planning and implementation process of a network© 2009 Cisco Learning Institute. 29
    30. 30. Core Principles • Separation of duties: two-man control and dual operator • Rotation of duties • Trusted recovery: failure preparation and system recovery • Change and configuration controls© 2009 Cisco Learning Institute. 30
    31. 31. Separation of Duties© 2009 Cisco Learning Institute. 31
    32. 32. Rotation of Duties Technical support Week 1 Week 2 Data Center Support Week 3 Data Entry© 2009 Cisco Learning Institute. 32
    33. 33. Trusted Recovery Practices: • A junior staff member is responsible for loading blank media. • Backup software uses an account that is unknown to individuals to bypass file security. • A different staff member removes the backup media and securely stores it on site while being assisted by another member of Backup 3 Backup 2 the staff. • A separate copy of the backup is stored off Backup 1 site and is handled by a third staff member who is accompanied by another staff member.© 2009 Cisco Learning Institute. 33
    34. 34. Configuration Change Control There are five steps in a change control process: 1.Apply to introduce the change. 2.Catalogue the proposed change. 3.Schedule the change. 4.Implement the change. 5.Report the change to relevant parties.© 2009 Cisco Learning Institute. 34
    35. 35. Objectives of Security Testing andEvaluation Objectives of ST&E: Uncover design, implementation, and operational flaws that could lead to the violation of the security policy. Determine the adequacy of security mechanisms, assurances, and device properties to enforce the security policy. Assess the degree of consistency between the system documentation and its implementation.© 2009 Cisco Learning Institute. 35
    36. 36. Assessing the Operational Status • Network scanning • Vulnerability scanning • Password cracking • Log review • Integrity checkers • Virus detection • War dialing • War driving (802.11 or wireless LAN testing) • Penetration testing© 2009 Cisco Learning Institute. 36
    37. 37. Using Testing Results • As a reference point for corrective action • To define mitigation activities to address identified vulnerabilities • As a benchmark to trace the progress of an organization in meeting security requirements • To assess the implementation status of system security requirements • To conduct cost and benefit analysis for improvements to system security • To enhance other activities such as risk assessments, Certification and Authorization (C&A), and performance improvement efforts© 2009 Cisco Learning Institute. 37
    38. 38. Security Testing Tools • Nmap: – discovers computers and services on a computer network, thus creating a map of the network. • GFI LANguard: network and security scanner which detects vulnerabilities. • Tripwire: assesses and validates IT configurations against internal policies, compliance standards, and security best practices • Nessus: vulnerability scanning software, focusing on remote access, misconfiguration passwords, and DoS against the TCP/IP stack. • L0phtcrack: password auditing and recovery application. • Metasploit: provides information about vulnerabilities and aids in penetration testing and IDS signature development. • SuperScan: port scanning software designed to detect open TCP and UDP ports and what services are running on those ports© 2009 Cisco Learning Institute. 38
    39. 39. Nmap Basic functionality • Classic TCP and UDP port scanning • Classic TCP and UDP port sweeping • Stealth TCP and UDP port scans and sweeps • Remote operating system identification, known as OS fingerprinting.© 2009 Cisco Learning Institute. 39
    40. 40. SuperScan • Improved host detection using multiple ICMP methods • TCP SYN scanning • UDP scanning (two methods) • Source port scanning • Fast hostname resolving • Extensive banner grabbing • IP and port scan order randomization • Extensive Windows host enumeration capability© 2009 Cisco Learning Institute. 40
    41. 41. Continuity Planning Objectives • Moving or relocating critical business components and people to a remote location while the original location is being repaired • Utilizing different channels of communication to deal with customers, shareholders, and partners until operations return to normal© 2009 Cisco Learning Institute. 41
    42. 42. Disaster Recovery • The process of regaining access to the data, hardware, and software necessary to resume critical business operations after a disaster. • Plan for coping with unexpected or sudden loss of key personnel.© 2009 Cisco Learning Institute. 42
    43. 43. Disruptions • Identify types of disasters or disruptions possible • Take into account the magnitude of the disruption© 2009 Cisco Learning Institute. 43
    44. 44. Backups • Redundancy - Replacement components owned by the organization or a server provider - Service level agreement (SLA) • Redundant facility - Hot Site - Warm Site - Cold Site© 2009 Cisco Learning Institute. 44
    45. 45. System Development Life Cycle (SDLC)Initiation Initiation Security categorization: This task defines threeAcquisition and Disposition levels of potential Development impact on organizations or individuals should there be a breach of security: low, moderate, and high,. Security categorization standards help organizations make the appropriate selection of security controls for their information systems. Preliminary risk assessment: This task results in an initial description of the basic security needs of the system. A preliminary risk assessment should define the threat environment in which the system Operations and will operate. Implementation Maintenance© 2009 Cisco Learning Institute. 45
    46. 46. Acquisition and Development Risk assessment: an analysis that identifies the protection requirements Initiation for the system through a formal risk assessment process. Security functional requirements: an analysis of requirements Security assurance requirements: an analysis of the requirements that address the developmental activities that are required and the assurance Disposition Acquisition and evidence that is needed to produce the desired level of confidence Development Security cost considerations and reporting: determines how much of the development cost to attribute to information security Security planning: new and current agreed upon security controls should be fully documented. Security control development: ensures that the security controls that the respective security plans describe are designed, developed, and implemented. Operations and Developmental security test and evaluation: ensures that security Maintenance Implementation controls that are developed for a new information system are working properly and are effective.© 2009 Cisco Learning Institute. 46
    47. 47. Implementation Inspection and acceptance: ensures that the organization validates and Initiation verifies that the functionality that the specification describes is included in the deliverables. System integration: ensures that the system is integrated at the operational site where the information system is deployed for operation. Security certification: ensures that one effectively implements the Disposition Acquisition and controls through established verification techniquesDevelopment and procedures. Security accreditation: provides the necessary security authorization of an information system to process, store, or transmit information that is required. Operations and Maintenance Implementation© 2009 Cisco Learning Institute. 47
    48. 48. Operations and Maintenance Initiation Configuration management and control: ensures that there is adequate consideration of the potential security impacts due to specific changes to an information system or its surrounding environment. Disposition Acquisition and Continuous monitoring: ensures that controls continue to be Development effective in their application through periodic testing and evaluation. Operations and Maintenance Implementation© 2009 Cisco Learning Institute. 48
    49. 49. Disposition Initiation Disposition Acquisition and Development Information preservation: ensures that information is retained, as necessary, to conform to current legal requirements and to accommodate future technology changes that can render the retrieval method obsolete. Media sanitization: and Operations ensures that data is deleted, erased, and written over, as necessary. Maintenance Implementation Hardware and software disposal: ensures that hardware and software is disposed of as directed by the information system security officer.© 2009 Cisco Learning Institute. 49
    50. 50. Determining an Organization’s Assets Ask the following questions: • What does the organization THREATS have that others want? • What processes, data, or information systems are critical to the organization? • What would stop the organization from doing business or fulfilling its mission? Security Policies are designed to protect assets© 2009 Cisco Learning Institute. 50
    51. 51. Security Policy Benefits • Demonstrates an organization’s commitment to security. • Sets the rules for expected behavior. • Ensures consistency in system operations, software and hardware acquisition and use, and maintenance. • Defines the legal consequences of violations. • Gives security staff the backing of management.© 2009 Cisco Learning Institute. 51
    52. 52. Audience • Anyone with access to the network - Internal audience - External audience • Determines the content of the policy© 2009 Cisco Learning Institute. 52
    53. 53. Hierarchy of Policies Governing Policy Technical End-User Policies Policies© 2009 Cisco Learning Institute. 53
    54. 54. Governing Policy Important components: • A statement of the issue that the policy addresses. • How the policy applies in the environment. • The roles and responsibilities of those affected by the policy. • The actions, activities, and processes that are allowed and those that are not. • The consequences of noncompliance.© 2009 Cisco Learning Institute. 54
    55. 55. Technical Policies • General policies • E-mail policies • Remote -access policies • Telephony policy • Application policies • Network policies • Wireless communication policy© 2009 Cisco Learning Institute. 55
    56. 56. End User Policy • Cover all rules pertaining to information security that end users should know about, comply with, and implement. • May overlap with technical policies.© 2009 Cisco Learning Institute. 56
    57. 57. Standards, Guidelines, andProcedures • The security policy documents are high-level overview documents • Standards, guidelines, and procedures contain the actual details defined in the policies • Each document serves a different function, covers different specifications and targets a different audience© 2009 Cisco Learning Institute. 57
    58. 58. Standards Documents Standards documents include the technologies that are required for specific uses, hardware and software versioning requirements, program requirements, and any other organizational criteria© 2009 Cisco Learning Institute. 58
    59. 59. Guideline Documents • Provide a list of suggestions • Provide flexibility • Not usually mandatory • Sources: - National Institute of Standards and Technology (NIST) Computer Security Resource Center - National Security Agency (NSA) Security Configuration Guides - The Common Criteria standard© 2009 Cisco Learning Institute. 59
    60. 60. Procedure Documents Procedure documents include the details of implementation, usually with step-by-step instructions and graphics© 2009 Cisco Learning Institute. 60
    61. 61. Management Responsibilities Executive-level management must always be consulted during security policy creation in order to ensure the policy is comprehensive, cohesive, and legally binding.© 2009 Cisco Learning Institute. 61
    62. 62. Executive Titles • Chief Technology Officer (CTO)—Identifies and evaluates new technologies and drives new technology development Maintains and enhances current enterprise systems. • Chief Information Officer (CIO)—Responsible for the information technology and computer systems that support enterprise goals, to include successful deployment of new technologies and work processes. • Chief Security Officer (CSO)—Develops, implements and manages the organization’s security strategy, programs, and processes associated with all aspects of business operation including intellectual property. • Chief Information Security Officer (CISO)—Develops and implements security policy. .© 2009 Cisco Learning Institute. 62
    63. 63. Security Awareness Program • Reflects the business needs of an organization • Informs users of their IT security responsibilities • Explains all IT security policy and procedures • Explains proper rules of behavior for the use of the IT systems and data • Details sanctions for noncompliance Security Awareness • Components Program - Awareness campaigns - Training and education© 2009 Cisco Learning Institute. 63
    64. 64. Awareness Methods for increasing awareness: •Lectures, videos •Posters, newsletter articles, and bulletins •Awards for good security practices •Reminders such as login banners, mouse pads, coffee cups, and notepads© 2009 Cisco Learning Institute. 64
    65. 65. Training and Education From: IT department To: all Employees Subject: Course Offerings We are currently offering several training opportunities. Please see the list below and contact your manager if interested.© 2009 Cisco Learning Institute. 65
    66. 66. Success A successfully implemented security awareness program measurably reduces unauthorized actions by insiders, increases the effectiveness of existing controls, and helps fight waste, fraud, and abuse of information systems resources.© 2009 Cisco Learning Institute. 66
    67. 67. Laws and Ethics • Types of Laws - Criminal - Civil - Administrative • Ethics - Computer Ethics Institute - Internet Activities Board (IAB) - Generally Accepted System Security Principles (GASSP) - International Information Systems Security Certification Consortium, Inc (ISC)2 Code of Ethics© 2009 Cisco Learning Institute. 67
    68. 68. The ISC2 Code of Ethics • Code of Ethics Preamble Safety of the commonwealth, duty to our principals, and to each other requires that we adhere, and be seen to adhere, to the highest ethical standards of behavior. Therefore, strict adherence to this Code is a condition of certification. • Code of Ethics Canons - Protect society, the commonwealth, and the infrastructure. - Act honorably, honestly, justly, responsibly, and legally. - Provide diligent and competent service to principals. - Advance and protect the profession.© 2009 Cisco Learning Institute. 68
    69. 69. Motive, Opportunity, and Means • Motive answers the question of why a person (or persons) committed the illegal act. • Opportunity answers the question of when and where the person committed the crime. • Means answers the question of how the person committed the crime.© 2009 Cisco Learning Institute. 69
    70. 70. Forensics Procedures • Proper data collection • Data chain of custody • Data storage • Data backups© 2009 Cisco Learning Institute. 70
    71. 71. © 2009 Cisco Learning Institute. 71