UAB

Cyber Security Ini1a1ve

Purpose of the Cyber Security Ini1a1ve?

To provide a secure Compu1ng Environment

Single Source
Individual for Inventory
Mechanisms and Asset
Management

Current
Secured
Repor1ng
Environment
Environment
MicrosoC System Center Congura1on Manager
Campus SCCM
Overview
Why MicrosoC SCCM?

Inventory collec1on for mul1ple OS plaHorms

Key SCCM Features
Asset Intelligence and Inventory
Endpoint Protec1on
SoCware Update Management
Remote Management
Establishing a Campus Environment
September 2014

December 2014

Current
November 2014
Built and Expanded Department Collec1ng
Deployed the SCCM Integra1on Inventory for
SCCM Environment & Pilot 2000+
Environment to support Kicked O Systems
campus
ini1a1ve
Campus SCCM Readiness Criteria

Public or NAT IP Addresses

General SCCM not currently deployed
Factors Systems can ini1ate communica1on with
SCCM

OS Windows 7 / Windows 2003 or Later

Requirements Supported versions of Mac / Linux / Unix

Systems have 500 MB Free (5 GB

Disk Space
Preferred)
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

Campus SCCM Benets
Features and Roadmap
MicrosoC SCCM Features

Computer Asset Repor1ng

Remote Management

Managing Virus Protec1on

Deploying MicrosoC Updates

Campus MicrosoC SCCM Roadmap

Applica1on Deployment
Opera1ng System Deployment

Managing Congura1on Se`ngs

Reloca1ng User Proles

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

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 (www.quickstart.com).
 Pilot Review
School of Engineering
School of Engineering Environment

31 Servers
(Windows, Linux)

Custom
420 Desktop Computers soCware &
hardware
(Windows, Mac, Linux) management
tool

VDI for 300 concurrent

desktops
Why we chose SCCM?

We were invited to par1cipate in the pilot

by Interim VP of IT, Je Neyland.

We wanted a management system that

was more o the shelf than custom
wrifen.

We were looking for ecient use of IT

Sta 1me.
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.
Current Benets

Able to manage patched and unpatched

machines more eec1vely

Remote control has been eec1ve when

suppor1ng users at dierent loca1ons across
campus

Ease of monitoring of An1-virus ac1vity

Moving ahead with SCCM

Addi1onal Training to unlock and gain

knowledge of the full poten1al that SCCM has
to oer
Applying 3rd party updates and soCware
installa1on
Suppor1ng installa1on of soCware and
updates on Macs
Crea1ng custom reports
Cyber Security Ini1a1ve
Next Steps for Campus
What is next?
Timeline for repor1ng
August 14th repor1ng only
August 21st installing SCCM

Scheduling Installa1ons

Prepare nal report for campus review prior to

UA system mandate date
Develop Advisory Teams

Guidelines for iden1fying and

repor1ng sensi1ve data

Guidelines for risk mi1ga1on

Guidelines for maintaining and

adding hardware
Together Create Campus Ac1on Plan

Iden1fying sensi1ve data

Risk mi1ga1on of reported inventory
Adop1ng a single SCCM solu1on for the en1re
campus
Ques1ons?