PCI Compliance Update

Presented by: Jeff Gassaway, Information Security Officer – CISSPLucas Walker, Information Security Analyst – GSEC

1

2

The Way We Were

• FY 2012-2013• Improved oversight and direction• Improved compliance with PCI data security standards• Improved campus-wide security controls

3

What We Did to Improve

1. Brought CoalFire on site for departments with largest volume and highest risk PCI transactions.

2. Established PCI mailing list to facilitate communication

3. Brought PCI trainings to campus

4. Created PCI Working Group

4

• Based on number of transactions per year

• How credit cards are being taken

• Essentially, risk to the consumer

How We Reduced Costs

• Reduced reliance on CoalFire’s services• Shadowed CoalFire site visits and interviews

• Assisted departments in utilizing CoalFire’s tools• Navis• LightHouse

• PCI Working Group• Working to develop standard solutions to meet a variety of

departmental needs • Provide guidance• Consistency 5

Where We Are

• Reducing Scope and Complexity

• Clarifying PCI terms

• Bringing significant issues to PCI Working group:

• Developing approved enterprise solutions

• Advising on business processes changes

• Researching and supporting common tools and technology

• Reviewing and enhancing policies and procedures

• Cost Reduction6

Where We Must Go

• Quarterly scans (internal and external) conducted

• Robust change and patch management implemented

• Everything in scope logged and reviewed daily

• Consistent policies developed

• Annual departmental policy review and trainings conducted

• No cards stored

• No non-compliance7

Q&A• Help.unm.edu

• security@unm.edu

• kmellor@unm.edu

• Policy 7215

• it.unm.edu/security

8