Presentation is loading. Please wait.

Presentation is loading. Please wait.

Office of Campus Information Security Driving a Security Architecture by Assessing Risk Stefan Wahe Sr. Information Security Analyst.

Similar presentations


Presentation on theme: "Office of Campus Information Security Driving a Security Architecture by Assessing Risk Stefan Wahe Sr. Information Security Analyst."— Presentation transcript:

1 Office of Campus Information Security Driving a Security Architecture by Assessing Risk Stefan Wahe (smwahe@wisc.edu) Sr. Information Security Analyst

2 Realizing our Principles Answering the question, “Why?” To have a common understanding of building a secure architecture. Developed based on NIST 800-27,, ISO 20071, CIC schools, and other publications.

3 OCIS IT Security Principles 4.Security is a Common Understanding –Due Diligence; Manage Threats, Risks, and Costs; and Incident Management. 3.Security is Asset Management –Classify Information; Least Privilege; and Separation of Duties. 2.Security is Part of the Development Life Cycle –Information Privacy and Assurance; Usability; and Defense in Depth. 1.Security is Everyone’s Responsibility

4 Risk Assessment Process Step 1: Letter of Engagement Step 2: Conduct the Assessment Step 3: Draft Report on Findings Step 4: Communicate Findings Step 5: Re-Assess

5 Building a Common Understanding: Managing Risk Risk ImpactLikelihood Mitigation Controls $ Care $ $

6 Example Question Does the system maintain Configuration Management methodology that includes: 1.A documented process for reviewing, approving and implementing changes 2.Version control for software system components 3.Timely identification and installation of all applicable patches for any software used in the provisioning of the CS.

7 Common Gaps Common Security Gaps (examples) –The system infrastructure needs to be segmented with robust firewall controls. –Encryption controls and key management procedures should be implemented for data at rest. –Restricted data needs to be sanitized in non- production environments. –Intrusion detection, prevention and log management devices should be installed and maintained with appropriate alerting processes.

8 Integrating a Security Culture Awareness and Training –SANS Secure Web Development Policy Development and Best Practices –Restricted Information Management Practices –Desktop Encryption Policy Centralized Resources –Security Event Management –Network Management –Desktop Tools –PKI

9 Questions How can we help you?


Download ppt "Office of Campus Information Security Driving a Security Architecture by Assessing Risk Stefan Wahe Sr. Information Security Analyst."

Similar presentations


Ads by Google