Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
6Activity
0 of .
Results for:
No results containing your search query
P. 1
Chronology of the SC hacking investigtation

Chronology of the SC hacking investigtation

Ratings: (0)|Views: 7,135 |Likes:
Published by Richard Phelps
Read the state of South Carolina's chronology of the investigation into a state Department of Revenue data breach that exposed 3.6 million social security numbers.
Read the state of South Carolina's chronology of the investigation into a state Department of Revenue data breach that exposed 3.6 million social security numbers.

More info:

Published by: Richard Phelps on Oct 26, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

12/04/2012

pdf

text

original

 
Chronology
October 10:
• The
SC
Department
of
Revenue was informed
by
the South Carolina Division
of
Information Technology
(DSIT)
of
a potential cyber attack involving the personal information
of
taxpayers.
DOR
worked
with
DSIT
throughout the day
to
determine what may have happened and what stepsneeded
to
be taken immediately
to
deal
with
the situation.
DOR
consulted with state and federal law enforcement agencies
for
guidance.
Law
enforcement recommended several steps
to
be
taken, including consulting the nation's
top
cybersecurity firms.
DOR
assessed
the top
3 recommendations from law enforcement and contacted Mandiant
of
Alexandria,
VA.
DOR
contacted the Governor's office.
SLED
Chief
Keel
briefed Governor Haley.
October 11:
DOR
met
with
the Governor's office in the morning
to
give her a full briefing, including laying
out
our
4-pronged approach:o Contract with Mandiant, which we signed on October
12
with
the approval
of
the Governor, tofind and fix the leak;o Conduct
an
internal investigation
of
all outside contractors and certain employees
to
see
if
theyhave been involved with any security breaches;o Develop
of
a public notification plan;o Institute additional protection tools on
our
system.
DSIT
began monitoring
DOR
and its main servers
to
detect any unauthorized intrusions.
DOR
made the decision
that
if
DSIT
or
DOR
identified any unusual exfiltrations
of
data, the systemimpactedwould
be
shut down immediately.
October 12:
DOR
signed a contract
with
Mandiant.Mandiant began working on plans to
send
surveillance and monitoring tools
to
be
installed at
DOR
in Sc.
October 15:
DOR
worked
with
Mandiant to begin installing surveillance and monitoring equipment which wascompletely in place within
48
hours.
DOR
began daily status update calls
with
complete team, including representatives from lawenforcement,
DSIT,
DOR,
Mandiant-the first call was planning session.
October 16:
Mandiant began deploying a monitoring agent on every computer workstation throughout
DOR,
aprocess was completed by October 20.

Activity (6)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
Georg P. Mueller liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->