Griffith and the 2014 G20 IT Security response to the 2014 G20 - - PowerPoint PPT Presentation

▶
griffith and the 2014 g20
SMART_READER_LITE
LIVE PREVIEW

Griffith and the 2014 G20 IT Security response to the 2014 G20 - - PowerPoint PPT Presentation

Sep 28, 2022 198 likes •375 views

Griffith and the 2014 G20 IT Security response to the 2014 G20 Summit Greg Vickers Senior Project Manager INS About Griffith Closely involved in G20 Summit in Brisbane 5 campuses, South Bank campus within a kilometer of the G20

slide-1
SLIDE 1

INS

Griffith and the 2014 G20

IT Security response to the 2014 G20 Summit Greg Vickers

Senior Project Manager

slide-2
SLIDE 2

INS

About Griffith

  • Closely involved in G20 Summit in

Brisbane

  • 5 campuses, South Bank campus within a

kilometer of the G20 Summit location

  • Some G20 events held at South Bank

campus

  • ~46,000 students (2014)
  • ~10,000 staff (2014)
  • lots of endpoints
  • 10Gb Internet connection
slide-3
SLIDE 3

INS

G20 and Development Conference

slide-4
SLIDE 4

INS

Target

slide-5
SLIDE 5

INS

Risks

  • Risks identified to public and student facing

systems

  • Breach, defacement, data loss, etc
  • Front page of a newspaper or website
  • Insider threat
slide-6
SLIDE 6

INS

Mitigations

  • Managed Security Service (Symantec)
  • Cloud-based Application Firewall (Akamai)
  • Hosted DDoS protection (Akamai)
  • Existing Unified Threat Management

system

  • 24/7 attention paid to all new and existing

mitigation processes during, before and after Summit

slide-7
SLIDE 7

INS

Implementation - MSS

  • Fairly easy to implement
  • Low potential impact on staff/students from

required changes

  • Point-and-click user interface
  • Good graphic views into our data
  • Six month engagement
slide-8
SLIDE 8

INS

Implementation - Hosted DDoS

  • Fairly easy to implement
  • Low potential impact on staff/students from

required changes

  • Point-and-click user interface
  • Four month engagement
slide-9
SLIDE 9

INS

Implementation - Application Firewall

  • High difficulty to implement
  • High potential impact on staff/students from

required changes

  • Point-and-click user interface
  • Four month engagement
slide-10
SLIDE 10

INS

Implementation - Application Firewall

  • Pace of project brought scope changes
  • 19 web sites, three months (unheard of)
  • Blackboard
  • CMS/Intranet
  • ERP system
  • SSO, Exams/Timetabling
  • DNS Registrar changes
  • Akamai and Griffith DNS connected at

the hip (risk of Akamai DNS failure)

slide-11
SLIDE 11

INS

Implementation - Application Firewall

slide-12
SLIDE 12

INS

Implementation - Application Firewall

  • Testing:
  • Alternate DNS entry created to point at

production

  • Web service/site owner engaged to test

functionality on their production site/data

  • Internal IT Security specialists worked

with owners and vendor technicians on configuration

slide-13
SLIDE 13

INS

Implementation - Application Firewall

  • Potential Very High impact on staff or

student services

  • Brought some speed increases to static

content

  • Web team investigations found delivery

delays in Griffith homepage

  • Protected against Internet-based attacks
  • Decommissioning easy (too easy!)
slide-14
SLIDE 14

INS

Implementation - UTM

  • Fairly easy to implement, had much

attention from networking staff

  • Some potential impact on staff/students

from required changes, but managed closely

  • Familiar user interface
  • Ongoing (existing) engagement
slide-15
SLIDE 15

INS

Obligatory graph

  • Raised profile of Griffith in the international

bad guy community

slide-16
SLIDE 16

INS

Success!

  • No web sites defaced
  • No successful attacks detected
  • No mass malware outbreak
  • No newspapers or web site for the wrong

reason

slide-17
SLIDE 17

INS

FIN

Thank you! Questions?