UAB Cyber Security Ini1a1ve

Transcription

1 UAB Cyber Security Ini1a1ve

2 Purpose of the Cyber Security Ini1a1ve? To provide a secure Compu1ng Environment Individual Mechanisms Single Source for Inventory and Asset Management Current Repor1ng Environment Secured Environment

3 MicrosoC System Center Configura1on Manager

4 Campus SCCM Overview

5 Why MicrosoC SCCM? Inventory collec1on for mul1ple OS plahorms Key SCCM Features Asset Intelligence and Inventory Endpoint Protec1on SoCware Update Management Remote Management

6 Establishing a Campus Environment September 2014 Built and Deployed SCCM Environment November 2014 Expanded the SCCM Environment to support campus ini1a1ve December 2014 Department Integra1on & Pilot Kicked Off Current Collec1ng Inventory for Systems

7 Campus SCCM Readiness Criteria General Factors OS Requirements Disk Space Public or NAT IP Addresses SCCM not currently deployed Systems can ini1ate communica1on with SCCM Windows 7 / Windows 2003 or Later Supported versions of Mac / Linux / Unix Systems have 500 MB Free (5 GB Preferred)

8 Campus SCCM Agent Deployment Process Complete Readiness Survey & Address Gaps Submit AskIT Ticket to Par1cipate Determine SCCM Agent Deployment Methods Test SCCM Agent Deployments Deploy SCCM Agents Complete Feedback Survey

9 Campus SCCM Benefits Features and Roadmap

10 MicrosoC SCCM Features Computer Asset Repor1ng Remote Management Managing Virus Protec1on Deploying MicrosoC Updates

11 Campus MicrosoC SCCM Roadmap Applica1on Deployment Opera1ng System Deployment Managing Configura1on Se`ngs Reloca1ng User Profiles

12 Role Based Access Administrators with the same Security Roles are s1ll limited to the objects they can manage by Scope SCCM Security Roles SCCM Security Scopes

13 Assistance and Training UAB IT will partner with you throughout the en1re deployment process and is available to answer any ques1ons you may have. We can provide training videos & addi1onal documenta1on as needed. For professional training, we recommend Quickstart (

14 Pilot Review School of Engineering

15 School of Engineering Environment 31 Servers (Windows, Linux) 420 Desktop Computers (Windows, Mac, Linux) Custom socware & hardware management tool VDI for 300 concurrent desktops

16 Why we chose SCCM? We were invited to par1cipate in the pilot by Interim VP of IT, Jeff Neyland. We wanted a management system that was more off the shelf than custom wrifen. We were looking for efficient use of IT Staff 1me.

17 Our Implementa1on Experience Ini1al mee1ng with SCCM team Comple1on of Readiness Survey Deployed SCCM Client across network via custom script Upgraded An1virus protec1on to Endpoint Created Collec1ons for All ENG machines as well as by Department. Added policies to control which collec1on(s) should be allowed to receive An1virus update, patches, and Remote Control.

18 Current Benefits Able to manage patched and unpatched machines more effec1vely Remote control has been effec1ve when suppor1ng users at different loca1ons across campus Ease of monitoring of An1- virus ac1vity

19 Moving ahead with SCCM Addi1onal Training to unlock and gain knowledge of the full poten1al that SCCM has to offer Applying 3 rd party updates and socware installa1on Suppor1ng installa1on of socware and updates on Macs Crea1ng custom reports

20 Cyber Security Ini1a1ve Next Steps for Campus

21 What is next? Timeline for repor1ng August 14 th repor1ng only August 21 st installing SCCM Scheduling Installa1ons Prepare final report for campus review prior to UA system mandate date

22 Develop Advisory Teams Guidelines for iden1fying and repor1ng sensi1ve data Guidelines for risk mi1ga1on Guidelines for maintaining and adding hardware

23 Together Create Campus Ac1on Plan Iden1fying sensi1ve data Risk mi1ga1on of reported inventory Adop1ng a single SCCM solu1on for the en1re campus

24 Ques1ons?