{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

csce548-lect5.b - CSCE 522 Building Secure Software...

Info icon This preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
CSCE 522 CSCE 522 Building Secure Software Building Secure Software
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CSCE 548 - Farkas 2 Reading Reading This lecture McGraw: Ch. 3 G. McGraw, Software Security , http://www.cigital.com/papers/download/bsi1-swsec.pdf Ted Demopoulos, Worst Practices in Developing Secure Software, http://www.demop.com/articles/developing-secure-software.html Next Lecture McGraw: Ch. 4 (overview, we’ll cover code review in details later)
Image of page 2
CSCE 548 - Farkas 3 Three Pillars of Software Security Three Pillars of Software Security Risk Management Software Security Touchpoints Knowledge
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CSCE 548 - Farkas 4 Risk Management Risk Management How much effort to invest in security Consequences of security breaches Acceptable-level of security Tracking and mitigating risk throughout the full SDLC
Image of page 4
CSCE 548 - Farkas 5 Touchpoints Touchpoints System-wide activity: from design to testing and feedback Focus on security from ground up Touchpoints: 1. Code review 2. Architectural risk analysis 3. Penetration testing 4. Risk-based security testing 5. Abuse cases 6. Security requirements 7. Security operations 8. External Analysis
Image of page 5

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CSCE 548 - Farkas 6 Knowledge Knowledge Gathering, encapsulating, and sharing security knowledge Knowledge catalogs: principles, guidelines, rules, vulnerabilities, exploits, attack patterns, historical risks Knowledge categories: Prescriptive knowledge Diagnostic knowledge Historical knowledge Applied along the SDLC
Image of page 6
CSCE 548 - Farkas 7 Security Engineering Security Engineering Reduce the need for reactive technologies (e.g., intrusion detection) by safer products Understand software Need for: Software developers Operations people Administrators Users Executives
Image of page 7

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CSCE 548 - Farkas 8 Software Security Touchpoints Software Security Touchpoints Best Practices Both White Hat (constructive) and Black Hat (destructive) activities Throughout the SDLC
Image of page 8
CSCE 548 - Farkas 9
Image of page 9

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern