1 / 28

An Introduction to Information Assurance

An Introduction to Information Assurance. COEN 150 Spring 2007. Reading Assignment. Read section 3 of faq http://www.w3.org/Security/Faq/

denim
Télécharger la présentation

An Introduction to Information Assurance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. An Introduction to Information Assurance COEN 150 Spring 2007

  2. Reading Assignment • Read section 3 of faq http://www.w3.org/Security/Faq/ • CERT is a coordination center for Internet security operated by Carnegie Mellon. Read CERT article on security http://www.cert.org/encyc_article/tocencyc.html

  3. This course is part of the SCU Information Assurance curriculum which was recently certified by the Committee on National Systems Security of the National Security Agency as meeting the standards of the National INFOSEC Education and Training Program. http://www.nsa.gov/ia/academia/iace.cfm

  4. 4011 Certificate Requirements • BSCE: AMTH 387, COEN 250; 12 units from COEN 150, 178, 252, 253, 350, 351; and approved senior design project. • MSCE: AMTH 387, COEN 250, 252, 253, 351 and either COEN 350, 254, or 352.

  5. Terminology Overview • Attacks, Services and Mechanisms • Security Services • Threats, Attacks and Vulnerabilities • Security Policies and Mechanisms for Defense • Readings, standards, etc.

  6. Definitions • Security Attack:Any action that compromises the security of information. • Security Mechanism:A mechanism that is designed to detect, prevent, or recover from a security attack. • Security Service:A service that enhances the security of data processing systems and information transfers. A security service makes use of one or more security mechanisms.

  7. Security Services (Goals) • Confidentiality – concealment of information or resources. Includes whether or not data exists. Implies “authorization” so that only authorized people can access confidential data.

  8. Security Services (cont) • Integrity – the trustworthiness and the correctness of data or resources. • Usually in terms of preventing improper or unauthorized change. • Can have several types of integrity: data integrity and origin integrity • Was the email spoofed? • Two types of integrity services: prevention and detection.

  9. Security Services (cont) • Availability – the ability of authorized entities to use the information or resource. Denial of service attacks inhibit this service • CIA: Confidentiality, Integrity, Availability

  10. Vulnerabilities, Threats and Attacks • A vulnerability is a weakness in the system that might be exploited to cause loss or harm (and a violation of security services). • A threat is a potential violation of security. Security services counter threats. • An attack is the actual attempt to violate security. It is the manifestation of the threat.

  11. Classifying Communication Attacks

  12. Types of Attacks • Interruption: This is an attack on availability • Interception: This is an attack on confidentiality • Modification: This is an attack on integrity • Fabrication: This is an attack on integrity

  13. Additional Threats/Attacks • Repudiation of origin – a false denial that an entity sent or created something (I didn’t send that order to but Enron stock the day before it crashed). Attack on integrity • Denial of receipt – a false denial that an entity received some information or message. (I didn’t receive the diamond shipment). Attack on integrity and availability. • Denial of Service – long term inhibition of information or service. Attack on availability.

  14. Passive and Active Threats

  15. Security Policy and Mechanisms • A security policy is a statement of what is and is not allowed. • A security mechanism is a method, tool, or procedure for enforcing security policy. • These should clearly be separate things.

  16. Policy and Mechanism Example • Policy – only the systems administrator is allowed to access the password file and then only in encrypted form • Mechanism – the password file is not stored in clear text, but only in encrypted form with algorithm XYZ. The O.S. checks the access authorization of any process attempting to read the password file immediately before the access; whenever access is denied, that attempt is recorded in a log of suspicious activity.

  17. Security Mechanisms • Prevention, Detection, Recovery • Prevention: • Encryption • Software Controls (DB access limitations, operating system process protection) • Enforce policies (frequent password change) • Physical Controls • Detection: Intrusion detection systems (IDS)

  18. Prevention Mechanisms • Adequate prevention means that an attack will fail. Prevention usually involves mechanisms that the user cannot override. • Prevention mechanisms are often cumbersome and do not always work perfectly or fail because they are circumvented. • Passwords are a prevention mechanism to prevent unauthorized access. They fail when the password becomes known to a person other than the owner.

  19. Detection Mechanisms • Detection is used when an attack cannot be prevented and it also indicates the effectiveness of prevention measures. • The goal is to determine that an attack is underway or has occurred and report it. • Audit logs are detection mechanisms. When you log into the design center’s unix servers, it gives you the IP address of the last successful login.

  20. Recovery • Recovery has several aspects. The first is to stop an attack and repair the damage. • Another is to trace the evidence back to the attacker and discover the identity of the attacker (this could result in legal retaliation). • Yet another aspect is to determine the vulnerability that was exploited and fix it or devise a way of preventing a future attack.

  21. Example: Private Property • Prevention: locks at doors, window bars, walls round the property • Detection: stolen items are missing, burglar alarms, closed circuit TV • Recovery: call the police, replace stolen items, make an insurance claim …

  22. Example E-Commerce • Prevention: encrypt your orders, rely on the merchant to perform checks on the caller, don’t use the Internet (?) … • Detection: an unauthorized transaction appears on your credit card statement • Recovery: complain, ask for a new card number, etc. • Footnote: Your credit card number has not been stolen. Your card can be stolen, but not the number. Confidentiality is violated.

  23. Problems with Security Mechanisms • Laws and Customs - is it legal? Might not be legal to retaliate against an attacker. • Is it acceptable practice? How many hoops do we have to jump through to authenticate? • Is it convenient? Users with security needs are often not aware of vulnerabilities and will not put up with excessive cost and inconvenience.

  24. Other Terminology • CompuSec: computer security (protect computers and the information in them) • ComSec: communication security (protect information as it is transmitted) • OpSec: operations security (security policies and procedures)

  25. Non-required but Worth a Glance • Common vulnerabilities and Exposures http://www.cve.mitre.org/ • SANS top 20 vulnerabilities http://www.sans.org/top20/ • NIST Computer Security Resource Center http://csrc.nist.gov/

  26. What the Government is Doing • National Strategy to Secure Cyberspace http://www.whitehouse.gov/pcipb/

  27. What you can do Scholarships for IA study designated CAE http://www.c3i.osd.mil/iasp/studentsMain.htm http://cisr.nps.navy.mil/scholarships.html IA at SCU AMTH 387 Cryptology COEN 250 Info Security Management COEN 252 Computer Forensics COEN 253 Secure Systems Development COEN 350 Secure Distributed Systems COEN 351 Internet and E-Commerce Security

More Related