+ All Categories
Home > Documents > Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... ·...

Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... ·...

Date post: 25-Jun-2020
Category:
Upload: others
View: 0 times
Download: 0 times
Share this document with a friend
82
Building a Risk Management Framework for HIPAA & FISMA Compliance Anurag Shankar Center for Applied Cybersecurity Research Indiana University 2015 Technology Exchange October 6, 2015
Transcript
Page 1: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

BuildingaRiskManagementFrameworkforHIPAA&FISMA

ComplianceAnuragShankar

CenterforAppliedCybersecurityResearchIndianaUniversity

2015TechnologyExchangeOctober6,2015

Page 2: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Outline

1. Introduction2. HIPAA&FISMADemystified3. CyberCompliance:TheIUApproach4. Building&LeveragingaRiskManagementFramework5. Conclusion

Page 3: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

1.Introduction

Page 4: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Whyatalkoncompliance?

• Wehaveanewusercommunity- clinicalresearchers.• TheirresearchITaregrowingtoHPC,HPN,andHPS*scales.• MedicalschoolITcannotkeepup.• Theirdataislacedwithregulations(HIPAA,FISMA).

• Complianceisaforeignlanguage(tomostofus).• Wedealwiththeusualsuspects– physicalscientistsandengineers.• Regulationsarenotourforte.

*Highperformancecomputing,networkingandstorage

Page 5: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Compliancechallenges

• Fear,uncertainty,doubt.• Languagebarrier.• Lackofresources.• Localrisktolerance.• Riskownership.• Policy.

Page 6: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Thegoalsthismorning

• Learntospeakcompliance.• Bringregulationstoapractical,actionableplane.

Page 7: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

2.Regulations- HIPAAandFISMA

Page 8: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HIPAA

Page 9: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatisHIPAA?

• HealthInsurance Portability &Accountability Act.• ProvidestheabilitytotransferandcontinuehealthinsurancecoverageforAmericanworkersandtheirfamilieswhentheychangeorlosetheirjobs.

• EnforcedbytheOfficeforCivilRights(OCR)intheU.S.DepartmentofHealth&HumanServices(HHS).

Page 10: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HIPAATimeline

• Passedin1996,becamelawin2001.TheHIPAASecurityRulecameoutin2003.

• TheHealthInformationTechnologyforEconomic&ClinicalHealth(HITECH)Actof2006.

• TheHIPAAOmnibusFinalRuleof2013includedprovisionsfromHITECH&the2008GeneticInformationNondiscriminationAct(GINA).

Page 11: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

IsHIPAAallaboutpatientprivacy?

• No.Therearemanyothercomponents.• PrivacyisaddressedthroughtheHIPAAPrivacyRule,theHIPAASecurityRule,and breachnotificationrequirement.

• ThePrivacyRuledefineswhoHIPAAappliesto(acoveredentity),whatisprotected(protectedhealthinformation orPHI),andcoversdisclosuresofPHI.

• TheSecurityRulefocusesexclusivelyonprotectingelectronicPHI(ePHI)inanyform– atrest,intransit,underanalysis,etc.

Page 12: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatconstitutesPHI*?Patientinformationinanyform(paper,verbal,electronic)containinganyofthefollowing18identifiers:

1. Names2. Allgeographicsubdivisionssmallerthanastate,includingstreetaddress,city,county,precinct,zipcode,andtheir

equivalentgeocodes,exceptfortheinitialthreedigitsofazipcodeif,accordingtothecurrentpubliclyavailabledatafromtheBureauoftheCensus:(1)thegeographicunitformedbycombiningallzipcodeswiththesamethreeinitialdigitscontainsmorethan20,000people;and(2)theinitialthreedigitsofazipcodeforallsuchgeographicunitscontaining20,000orfewerpeopleischangedto000.

3. Allelementsofdates(exceptyear) fordatesdirectlyrelatedtoanindividual,includingbirthdate,admissiondate,dischargedate,dateofdeath;andallagesover89andallelementsofdates(includingyear)indicativeofsuchage,exceptthatsuchagesandelementsmaybeaggregatedintoasinglecategoryofage90orolder.

4. Telephonenumbers5. Faxnumbers6. Electronicmailaddresses7. SocialSecuritynumbers8. Medicalrecordnumbers9. Healthplanbeneficiarynumbers10. Accountnumbers11. Certificate/licensenumbers12. Vehicleidentifiersandserialnumbers,includinglicenseplatenumbers

PHI,whenproperlyde-identified,isnolongersubjecttoHIPAA

13. Deviceidentifiersandserialnumbers14. Webuniversalresourcelocators(URLs)15. Internetprotocol(IP)addressnumbers16. Biometricidentifiers,includingfingerandvoiceprints17. Fullfacephotographicimagesandanycomparableimages18. Anyotheruniqueidentifyingnumber, characteristicorcode

*Youmayalsohearthetermspersonallyidentifiableinformation(PII),individuallyidentifiablehealthinformation(IIHI), healthinformation,etc.,buttheyarenotcreatedequal.

Page 13: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

IsallidentifiablehealthinformationPHI?

• No,onlywhenitiswithinthehealthcarecontext.• Forinstance,

• identifiablehealthinformation(yoursorsomeoneelse’s)yousharepubliclyonFacebookisnotPHI(itisnotsubjecttoHIPAA).

• However,ifamedicalprofessional(doctor,nurse,etc.)sharesitpubliclyonFacebook,itisPHI andthussubjecttoHIPAA.SuchadisclosurewouldbeconsideredabreachunderHIPAA.

Page 14: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhodoesHIPAAapplyto?

• AHIPAA coveredentity (CE).• Onlyhealthcareproviders,healthplans,andhealthclearinghousesareconsideredcoveredentities.

• Universitiesareoftenhybrid coveredentities,meaningtheyhavebothnon-covered(e.g.theEnglishdept.)andcoveredcomponents(e.g.theStudentHealthCenter,SchoolofMedicine).

• HIPAAappliestotheentireCE(thelegalentity).ItistheCEthatfacespenaltieswhenaHIPAAviolationoccurs,notitsemployeesorsubunits.

Page 15: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

DoesHIPAAapplytome?

• Yes,if youserveacoveredentity,• eitherasaunitofyourcoveredentityor• asaBusinessAssociate,AND• youcreate,receive,transmit,ormaintainPHI.

• Youcannotsay“Ididn’tknowwehadPHI”.PlausibledeniabilitycanbequiteexpensiveunderHIPAA.

• Yourorganizationisnotacoveredentityifitisnotinvolvedinhealthcareoperationsdirectly.

Checkwithyourcompliancefolksorcounsel

Page 16: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatisaBusinessAssociate(BA)?

• A“apersonororganization,otherthanamemberofacoveredentity'sworkforce,thatperformscertainfunctionsoractivitiesonbehalfof,orprovidescertainservicesto,acoveredentitythatinvolvetheuseordisclosureofindividuallyidentifiablehealthinformation.”

• However,thereisa“conduitexception”whichexcludes”…thoseentitiesprovidingmerecourierservices,suchastheU.S.PostalServiceorUnitedParcelServiceandtheirelectronicequivalents,suchasinternetserviceproviders(ISPs)providingmeredatatransmissionservices.”

Page 17: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

BusinessAssociateAgreements

• HIPAAmandatesyoutohaveaBusinessAssociateAgreement(BAA)withBAs(sinceit’sadisclosureofPHI).TheBAsmusthaveBAAswiththeirBAs,andsoon.

• TheBAAmustincludelanguagestatingthattheBAwillprotectyourPHIandabidebyHIPAA.(SampleBAAsareatHHSsite.)

• YouareexpectedtododuediligencetoensurethattheBAcanprotectyourPHIasperHIPAA.

• TheBAsaresubjecttoHIPAAindependentlyiftheyhavePHI.SoaretheirBAs,allthewaydownthechain.

Page 18: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

BreachNotification

• HIPAAmandatesabreachofPHItobereportedtotheOCR&thoseaffectedwithin60days.

• Forbreachesinvolving>500individuals,localmediaoutletsmustalsobenotified.

• Itisforyoutodecidewhetherasecurityincidentrisestothelevelofabreach.

Page 19: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Enforcement

• HIPAAviolationscanresultincivilmonetarypenaltiesagainstacoveredentityand/orcriminalpenaltiesagainstindividuals,withimprisonmentupto10years.

• Anauditmayoccurifthereisabreach.However,abreachisnotautomaticallyaHIPAAviolation.

• Auditsusedtooccuronlyinresponsetoabreachoracomplaint.TheOCRhasreceivedfundingtoinstitutearandomauditprogramnow.Theyaregettingreadyforthefirstroundofsuchaudits.

Page 20: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhenisabreachaHIPAAviolation?

ViolationsoccurswhentheCEisnotdoingduediligencerequiredunderHIPAAorignoringHIPAAaltogether:

• NotrespondingtotheOCRdespiterepeatedrequests.• Havingnoinformationsecurityprocesswhatsoever.• Noriskassessmentandmitigation.• Noincidentresponse.• Nodocumentation.• Notfollowingdocumentedpoliciesandprocedures.

TheOCRexpectsbreaches;thatisnotthepoint

Page 21: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

CivilMonetaryPenalties

*=Anactofomission inwhichacoveredentityorbusiness associateknew,orbyexercisingreasonablediligencewouldhaveknown,thattheactoromission violatedanadministrativesimplification(HIPAA)provision, butinwhichthecoveredentityorbusiness associatedidnotactwithwillfulneglect.

Thecostof“Ididn’tknowwehadPHI”.

*

Abreachof100patientrecords=100violations

Maximum“DidNotKnow”costofabreachof100patientrecords=$50Kx100=$5million!

Page 22: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

EnforcementinAction

Page 23: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheCorrectiveActionPlan(CAP)signedby IdahoStateUniversity

Breachesreportedbyuniversitiesì

Thepenaltiesarebad;reputationaldamage isworse

CorrectiveActionPlanforISU

Page 24: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatdoesHIPAAmeanforanITprovider?

• ToprotectePHIaspertheHIPAASecurityRule.

Page 25: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheHIPAASecurityRule

• TheSecurityRulerequires1.Administrative,2.Physical,and3.Technicalsafeguards to

• Ensuretheconfidentiality,integrity,and availabilityofallePHIcreated,received,maintainedortransmitted;

• Identifyandprotectagainstreasonablyanticipatedthreatstothesecurityor integrityoftheinformation;

• Protectagainstreasonablyanticipated,impermissibleusesordisclosures;

• Ensure compliancebytheworkforce;and• Provideameansformanagingriskinanongoingfashion.

Page 26: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

SecurityRuleSafeguards

• Administrative– securitymanagement/officer,workforcesecurity,incidentresponse,disasterplanning,evaluations,etc.

• Physical – facilitiesaccess,workstationuse/security,device/mediacontrols,etc.

• Technical – access/auditcontrol,integrity,authentication,transmissionsecurity,etc.

+organizational/policies/documentationrequirements

Page 27: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

RequiredandAddressable

• TheSecurityRulesafeguardsareeitherrequired oraddressable.• Required=whatitsays.• Addressable=mustbeinplace,butokifyouexplainwhyyoudon’thaveitinplaceand/orhowyouwillotherwiseaddresstherisk.

Page 28: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HIPAASafeHarbor

• Ifthedataisencryptedatrestandtheencryptionkeyisstoredseparatelyfromthedataandsecured,abreachneednotbereportedtotheOCR.

• ThisiscalledHIPAAsafeharbor.

Page 29: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

CanIbecertifiedHIPAAcompliant?

• No,HIPAAdoesn’tdefineathresholdwhereyouaresuddenlycompliant.

• TheOCRhasnotauthorizedanyonetocertifycompliance.• YoucangetthirdpartycertificationbuttheOCRdoesnotrecognizethem.Theymaystillfindyoulacking.

• Allyoucandoisexerciseduediligence- continuouslyassessandmitigaterisk.HIPAAcomplianceiseitherselfassertedorblessedbylocalauthorities.

Page 30: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HowdoIhandleHIPAAthen?

• Basedonyourenvironment,budget,andrisktolerance.• CheckifyourlocalHIPAAComplianceorInformationSecurityfolksalreadyhaveaprocessinplaceorhaverecommendations.Usetheirexpertise.

• SecuringtheePHIanddocumentationisstillyourtask.

Page 31: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

FISMA

Page 32: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatisFISMA?

FederalInformationSecurityManagementActof2002.

“Eachfederalagencyshalldevelop,document,andimplementanagencywideinformationsecurityprogramtoprovideinformationsecurityfortheinformationandinformationsystemsthatsupporttheoperationsandassetsoftheagency…”

Page 33: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhodoesFISMAapplyto?

• Governmentagencies,theirsubcontractors,orothersourcesthatservetheagencies.

Page 34: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhendoesFISMAapply?

• Whenyouuseagencysystemstomanageinformationonbehalfofanagency.

• Whenyouuseoroperateinformationsystemsonbehalfofanagency.• Ifyourcontractsaysitdoes.

Page 35: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HHSguidance

“FISMA'srequirementsfollowagencyinformationintoanysystemwhichusesitorprocessesitonbehalfoftheagency.Thatis,whentheultimateresponsibilityandaccountabilityforcontroloftheinformationcontinuestoresidewiththeagency,FISMAapplies.”

• Theterm"onbehalfof"indicatesthatonlythoseentitiesthatareacting,underagencyprinciples,asagents,whereHHS(oracomponent)istheprincipal,arecoveredbyFISMA.

Page 36: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

DoesFISMAapplytome?

• Probably,ifyouhaveacontractwithagovt.agency,e.g.NIH.• Checkthecontract;itwillexplicitlystateFISMArequirements.• CheckifFISMAlanguagehasbeenaddedtoexistingcontractswhentheyarerenewed.

• ItissometimespossibletonegotiateFISMAout.

Page 37: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatdoesFISMArequire?

• AdoptingtheNISTRiskManagementFramework(RMF).• Accreditation.• Regularreportingandreviews.

Page 38: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheFISMAWorkflow

Definesystemboundaries

AssessRisk(NIST800-30,37,39)

ApplyControls(NIST800-53)

EvaluateControls(NIST800-53A)

AuthoritytoOperate(ATO)

Page 39: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

DefineSystemBoundaries

• Alsoknownastheaccreditationboundaries.• Defineswherethe“system”beginsandends.• Asystemcanbeapartofanetwork,anapplication,alogicalcollectionofdisparatecomponents,etc.

• Aconceptualboundaryextendstoalldirectandindirectusersofthesystemthatreceiveoutput.

• RequiresITprofessionals.

Page 40: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

AssessRisk

• GuidancefromNISTdocumentsNIST800-30,37,and39isusedtoconductariskassessment.

• Individualrisksandseverityareidentified.• Aprioritizedlistofrisksiscreated.

Page 41: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

SelectControls

• TheresultsoftheriskassessmentandtheNISTcontrolcatalogNIST800-53areusedtoselectcontrolsthatmitigaterisk.

• Existingcontrolswillmitigatesomeoftherisk.Residualriskisaddressedbyaddingmissingcontrols.

• TheFISMAcontractwillspecifytherequiredsecuritycontrolbaseline(High,Medium,orLow).

Page 42: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

EvaluateControls

• Requiresregularassessments.• Involvestestingthecontrolsinplacetogaugetheireffectivenessinmitigatingrisk.

• Evaluationscanbeinternalorexternal.• TheNIST800-53AdocumentcoversevaluatingNIST800-53controls.

Page 43: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

AuthoritytoOperate(ATO)

• Thecompliancepaperworkissubmittedtotheagency.• AnATOletterisissuedbytheagencyauthorizingtheoperationofthesystem.

• Ifremediationisrequired,theagencymayissueanInterimAuthorityToOperate(IATO)withadefinedenddate.

+continuousmonitoringandregularreportingrequirements.

Page 44: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

WhatdoesittaketodoFISMA?

• Asignificantamountofeffortand$$.• DukeMedicine,oneacademicFISMAimplementation,estimatesthat,foreachPIcontract,ittakesthem~25hourstoreviewallthedocumentation,makesuggestedcontractualchangesforagencynegotiation,andcreateaFISMAmanagementplan.

• AseparatebudgetlineitemhastobeincludedinthecontracttocoverFISMAcosts.

• Manyuseacompletelywalledgarden.

Page 45: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

3.CyberCompliance:TheIUApproach

Page 46: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

History

• IUhasamatureresearchcyberinfrastructure (CI),servingbothlocalandnationalusers.

• ItisprovisionedthroughIU’scentralITorganization.• Itdeliverssupercomputing,datastorage/archival,visualization,applicationdevelopment&optimization,datamanagement,etc.

• Priorto2000,itwasusedalmostexclusivelybytheusualsuspects-physicalscientistsandengineers.

Page 47: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HIPAAintervenes

• ALillyEndowmentgrantin2000toaccelerategenomicsresearchatIUincludedusingtheexistingCIforIUSchoolofMedicineresearchers.

• HIPAAcomplianceforresearchsystemsbecamearequirement.• ForcedustolearnHIPAAandhowitaffectstheresearchworkflow.

Page 48: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Themostimportantcompliancestep

• WecreatedanoversightcommitteetooverseeourHIPAAeffortandputeverystakeholderonit– theComplianceOfficers,Counsel,CISO,SchoolofMedicinefaculty/ITstaff/CIO,CentralITseniormanagement,etc.

• Theybecameourambassadorsandstartedsendingclinicalresearchers,NIHgrantmoney,reflectedgloryourway.

Page 49: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Researchworkflow&compliance

Pre-Grant

•Prelim.Investigation• IRB•CIDesign

Proposal

•ProposalPreparation•BudgetPreparation•ProposalFunding

Execution

• DataAcquisition• DataAnalysis• Simulation• DataManagement• DataSharing• DataVisualization• DataPublishing

Post-Grant

• DataArchival•DataDisposal

Itwasusefultofollowtheresearchdataendtoend,throughitsentirelifecycle tounderstandwherecompliancetouchesit.

Stepsinredinvolvecompliance.

Page 50: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Evolution

• WeinitiatedaHIPAAspecific,homegrowncomplianceprocessin2008.• Itworkedwellinitially,butwastoorigidtoaccommodateotherrulesandregulationsappearingonthehorizon(e.g.FISMA).

• Thismotivatedsearchforastandards based,regulationneutralprocess.

• Theobviouschoicewasthewidelyused,highlyflexibleNIST standard.• Resultedinthecreationofasingle,reusable frameworkforcybercomplianceingeneral.

Page 51: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Howdoesitwork?

1. EstablishthebaseNISTRiskManagementFramework(RMF)2. Align withtheNISTstandard(notindividualregulation)3. Map theregulationtoNIST4. Addmissing*regulatorycontrols

Thisallowsscalinglaterallytocoveranyregulationorpotentialregulationchanges;allthatchangesaresteps2and3

*Regulatorycontrolsmissing fromNIST

Page 52: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HandlingHIPAA

1. AlignwiththeNISTlowsecuritybaseline2. MapHIPAAtoNISTusingNIST800-663. AddHIPAAsafeguardsmissingfromNIST

Page 53: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

HIPAAtoNISTMapping (fromNIST800-66)

Page 54: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

4.BuildingandLeveragingtheNISTRiskManagementFramework

Page 55: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Whatismanagingcyberrisk?

• Identify,assess,prioritize,andmitigaterisktoassetsonanongoingbasis.

• Focusesonrisk,calculatedasfollows.Risk={Threat/VulnerabilityxLikelihoodxImpact}

• Soabigthreatfromanexistingvulnerabilitythatishighlyunlikelytobeexploited/haslittleimpactislowrisk.Youdon’tkillyourselfoverit.

• Riskassessmentsharplyfocusesattentionandoptimizesresources.

Page 56: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Aren’tfirewalls,encryption,etc.enough?

• No.Technicalcontrolsareonlyonecomponentofcyberriskmanagement.Itrequiresamoreholisticapproach.

• WhynotencryptitallatrestandhaveHIPAAsafeharbor?Becauseit’snotalwayspossible,andyoustillhavetoprotectthekeyserver.

• TheNISTriskmanagementframeworkgivesuspreciselythat.

Page 57: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheNISTRMF

• Comprisesofthefollowing:

• Goodgovernance=institutionalsecurityorganization,policies,sanctions,enforcement

• Riskmanagement=assessment,mitigationthroughappropriatephysical,administrative,technicalcontrols

• Review =regularmonitoring,reviews,assessment,andmitigation• Awarenessandtraining• Documentation

Page 58: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

NISTSecurityLifecycle

Page 59: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

ButIdon’thaveresourcestodoallthat

• Youlikelyhavesomeorallofthese:• Aninformationsecurityoffice• InstitutionalITpolicies• Manysecuritycontrolsalreadyinplace• Documentation

• Thisisplentytostartwith.ItmeansthatyouhavethebasicelementsoftheNISTRMFinplacealready.

• Therestisaone-timeefforttoestablishtheRMF.Muchofitisdocumentation.

• Ariskassessmentenablesfurthereconomies.

Page 60: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

RiskAssessment

• Thebeginningoftheroadincyberriskmanagement.Youcannotmanageriskunlessyouknowwhatriskyouhave.

• Therearemanywaystoassessrisk,rangingallthewayfrompedestrian(&cheap)tohighlycomplex(&expensive).

• Youreffortshouldbecommensuratewithbudget,risktolerance,andorganizationalcomplexity.

Page 61: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

ImplementationSteps

1.AssignResources 2.Develop

tools3.Developprocess

4.Applyprocessto

newsystems

5.Migrateexisting

systemstonewprocess

Page 62: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Developprocess

1. Inventory2.

Documentation of System &

Controls

3. Risk Assessment

4. Risk Response

5. Awareness & Training

6. Oversight & Approval

7. Authority to Operate

8. Ongoing Risk

Management

Page 63: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Inventorywhatyouhave

• Systemdetails,ePHIlocation,securitysettings,BAAs,scaninfo,accessmethods,disposalinformation,etc.

• Software,version,patchlevel,BAAs,scaninfo,etc.• Privilegedaccessinventory- names,roles,datesauthorized,etc.• Incidentlog– incidentsummary,response.

Page 64: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Theinventorytemplate

Page 65: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Documentthesystemandcontrols

• ControlsaredocumentedintheSystemSecurityPlanorSSP.• IUtemplatebasedonwhatDHHS,NASA,etc.usetosatisfyFISMA.• Describessystemname,categorization,contacts,purpose,components,interconnections,boundaries,dependencies,andallNIST800-53security&privacycontrolsinplace.

Page 66: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheSSPtemplate

Page 67: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Documententerprisecommoncontrols

• IndividualSSPsdescribeNIST800-53controlsyouhaveinplace.• Manyofthesewillbeinheritedfromyourorganization.Theywillapplytoallsystems.Wecallthementerprisecommoncontrols(ECC).

• ItiswastefultoincludethemeverytimeineachSSP.• SodocumentECCsseparatelyandhaveindividualSSPssimplypointtotheECCdocs.

Page 68: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheECCdocumentisliterally

NIST800-53with

responses

Page 69: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Assessrisk

• Doriskself-assessments;theyarecheap• Havemanagers&systemadministratorssitdownandbrainstorm.• Identifyareasofvulnerabilitiesandriskforthesystem.• Documentriskareas,controlsthataddressthoserisks,residualrisks,andriskseverity.

• Haveexternal,thirdpartyassessmentseveryonceinawhileifyoucanaffordthem.

Page 70: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

TheRiskAssessmentReportTemplate

Page 71: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Documentriskresponse

• DocumenthowyouwillrespondtoresidualriskinaPlanofAction&MilestonesorPOA&M document.

• Itstateswhethertheriskwasaccepted,transferred,addressed,ortobemitigated,andreasons,timelinesandplannedmitigationactivities/controls.

• Validreasonsforacceptingariskisbudget,resourceconstraints,etc.Youcanoftenstilladdressthemthroughtraining.

Page 72: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

ThePOA&Mtemplate

Page 73: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Trainstaff

• Mandateannualtrainingforbothmanagementandstaffresponsibleforthesystem.

• AtIUthreee-trainingmodulesmustbecompleted:1. ThestandardIUHIPAAtraining(coveringthelawandIUpolicies&

procedures)2. IUHumanSubjectstraining3. UITSspecificinformationonhowHIPAAappliestotheIT

organizationspecifically,ourpolicies&NISTprocedures

• Documentallsecurityrelatedtraininginatraininglog.

Page 74: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Trainusersandraiseawareness

• Provideonlinetrainingandawarenessviaaknowledgebase,YouTubevideosorothermedia,inpersonclasses,andemailalerts.

• Candothingslikelaunchingyourownphishingattack.• Workindividuallywithusers,trainthemasyouhelpthem.• Helpthemcreatetheirown(HIPAA)documentationdescribinghowtheyareprotectingtheirend.

Page 75: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Instituteoversight/approval

• Haveyourauthoritiesprovideoversight(whichmayberequiredatyourinstitution)andapprovalorassignsomeonewithinyourorganization.

• AtIUthecompletedcompliancedocumentationpackageissenttotheIUHIPAAComplianceOffice,theUniversityInformationSecurityOffice,andInternalAudit.

Page 76: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Instituteongoingriskmanagement

• Instituteregular,ongoingriskmanagementthrough:• Regularreviews,riskre-assessments,anddocumentationupdates.• Continuous,automaticmonitoringofsystems.• Annualtraining&awareness.• Oversight.• Externalassessments.• Penetrationtesting.• Campaigns(phishing,etc.)

Page 77: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

4.Conclusion

Page 78: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Complianceisdoable

• Thegovernmentdoesnotexpectyoutoundertakeherculeanmeasuresorbuildwalledgardens.

• Cybercompliancerequirementsareallaboutbestpractices,somethingweshouldbedoinganyway(andare,mostly).

• Youlikelyhavesufficientlygoodinformationsecurityinplacealready.Itdoesn’ttakeagargantuanefforttogoalltheway.

Page 79: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Benefits

• AstandardsbasedRMFimplementationmakesyourule/regulationproof.

• Customerswithsensitivedatawilltrustyourshop,bringinginnewbusinessandfunding.

• Yourcompliancefolkswillsendpeopleyourway(oursdo).

• Youwillbetterserveresearchers/yourmission.

Page 80: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Theevolutionofcybersecurity

• Noonethinkscybersecurityisasolvableproblem;Thefixesaren’tworkingdespitehugecybersecuritybudgets.

• Anewapproachcalled“resilience”isemerging.• Ittreatsthesituationjustlikethemedicalestablishmentdoeshumandisease.Youwillbesick.Youwillbehacked.Period.

• Thegoalistosurvivebeinghacked,beresilient.• How?Prevent(defend,detect,remediate- baselineriskmanagement),Respond(incidentresponse),Recover(DR),andRefine(learn,adapt).

Page 81: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Links

• TheHIPAASecurityRule• http://www.hhs.gov/ocr/privacy/hipaa/administrative/securityrule/index.html

• NIST800-66:GuidetoImplementing theHIPAASecurityRule• http://csrc.nist.gov/publications/nistpubs/800-66-Rev1/SP-800-66-Revision1.pdf

• NIST800-53:RecommendedSecurityControls• http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final_updated-errata_05-01-2010.pdf

• NIST800-53A:GuideforAssessingSecurityControls• http://csrc.nist.gov/publications/nistpubs/800-53A-rev1/sp800-53A-rev1-final.pdf

• NISTHIPAASecurityRuleToolkit• http://scap.nist.gov/hipaa/

• NISTTemplates(emailme)

Page 82: Building a Risk Management Framework for HIPAA & FISMA ... › media › medialibrary › ... · • The Security Rule safeguards are either requiredor addressable. • Required =

Contact

[email protected]


Recommended