CERT Resilience Management Model, Version 1.0

More documents

Recommendations

Info

Technical Solution, the purpose of which is to design, develop, and implement solutionsto software and system requirements. Solutions, designs, and implementationsencompass software and system products, product components, and product-related lifecycleprocesses, either singly or in combination as appropriate.There are a growing number of reputable sources to consider when identifying and selectingcandidate guidelines for the development of resilient software and systems across the lifecycle, particularly for software security and assurance.These are examples of sources of guidelines: Building Security In Maturity Model (BSIMM2) v2.0http://www.bsi-mm.com/ Open Web Applications Security Project (OWASP) Software Assurance Maturity Model (SAMM) v1.0http://www.owasp.org/index.php/Category:Software_Assurance_Maturity_Model Microsoft’s Security Development Life Cycle, Version 4.1http://www.microsoft.com/security/sdl/Department of Homeland Security Assurance for CMMI Process Reference Modelhttps://buildsecurityin.us-cert.gov/swa/procwg.htmlThe Resilient Technical Solution Engineering process area assumes that the organizationhas one or more existing, defined processes for software and system development intowhich resilience controls and activities can be integrated. If this is not the case, theorganization should not attempt to implement the goals and practices identified in thisprocess area.Note: This process area does not address the unique aspects of the resilience of embeddedsystems or the resilience of hardware that is part of a software-intensive system.Related Process AreasResilience requirements for software and system technology assets in operation, includingthose that may influence quality attribute requirements in the development process, aredeveloped and managed in the Resilience Requirements Development and ResilienceRequirements Management process areas respectively.Identifying and adding newly developed and acquired software and system assets to theorganization’s asset inventory is addressed in the Asset Definition and Management processarea.The management of resilience for technology assets as a whole, particularly for deployed,operational assets, is addressed in the Technology Management process area. Thisincludes, for example, asset fail-over, backup, recovery, and restoration.Acquiring software and systems from external entities and ensuring that such assets meettheir resilience requirements throughout the asset life cycle is addressed in the ExternalDependencies Management process area. That said, RTSE specific goals and practicesshould be used to aid in evaluating and selecting external entities that are developingsoftware and systems (EXD:SG3.SP3), formalizing relationships with such external entities(EXD:SG3.SP4), and managing an external entity’s performance when developing softwareand systems (EXD:SG4).180 | CMU/SEI-2010-TR-012
Monitoring for events, incidents, and vulnerabilities that may affect software and systems inoperation is addressed in the Monitoring process area.Service continuity plans are identified and created in the Service Continuity process area.These plans may be inclusive of software and systems that support the services for whichplanning is performed.Summary of Specific Goals and Practices)GoalsRTSE:SG1 Establish Guidelines for ResilientTechnical Solution DevelopmentRTSE:SG2 Develop Resilient TechnicalSolution Development PlansRTSE:SG3 Execute the PlanPracticesRTSE:SG1.SP1 Identify General GuidelinesRTSE:SG1.SP2 Identify Requirements GuidelinesRTSE:SG1.SP3 Identify Architecture and Design GuidelinesRTSE:SG1.SP4 Identify Implementation GuidelinesRTSE:SG1.SP5 Identify Assembly and Integration GuidelinesRTSE:SG2.SP1 Select and Tailor GuidelinesRTSE:SG2.SP2 Integrate Selected Guidelines with a DefinedSoftware and System Development ProcessRTSE:SG3.SP1 Monitor Execution of the Development PlanRTSE:SG3.SP2 Release Resilient Technical Solutions intoProductionSpecific Practices by GoalRTSE:SG1 Establish Guidelines for Resilient Technical Solution DevelopmentGuidelines are developed to ensure proper consideration of resilienceactivities and controls in all phases of the life cycle.RTSE:SG1.SP1 Identify General GuidelinesGeneral guidelines for building resilience into software andsystems are identified.RTSE:SG1.SP2 Identify Requirements GuidelinesGuidelines for determining software and systems resiliencerequirements are identified.RTSE:SG1.SP3 Identify Architecture and Design GuidelinesGuidelines for designing resilience into software and systems areidentified.RTSE:SG1.SP4 Identify Implementation GuidelinesGuidelines for implementing resilient software and systems areidentified.RTSE:SG1.SP5 Identify Assembly and Integration GuidelinesGuidelines for the assembly and integration of resilient softwareinto resilient systems are identified.181 | CMU/SEI-2010-TR-012
Page 1 and 2:
CERT ® Resilience Management Model
Page 3 and 4:
Table of ContentsPrefaceAbstractvix
Page 5 and 6:
List of FiguresFigure 1: The Three
Page 7 and 8:
List of TablesTable 1: Process Area
Page 9 and 10:
AcknowledgementsThis report is the
Page 11 and 12:
The effect of increased levels of c
Page 13 and 14:
Part One: About the CERT ® Resilie
Page 15 and 16:
1 IntroductionOperational resilienc
Page 17 and 18:
experience, organizations often ask
Page 19 and 20:
continuity management, and IT opera
Page 21 and 22:
As a descriptive model, CERT-RMM fo
Page 23 and 24:
Table 1:Process Areas in CERT-RMM a
Page 25 and 26:
their ability to transform the way
Page 27 and 28:
2 Understanding Key Concepts in CER
Page 29 and 30:
Historically and often still today,
Page 31 and 32:
Operational resilience addresses th
Page 33 and 34:
esilience of services is key for mi
Page 35 and 36:
Figure 7: Impact of Disrupted Asset
Page 37 and 38:
owners are responsible for ensuring
Page 39 and 40:
into the “security” function bu
Page 41 and 42:
Figure 12: Software/System Asset Li
Page 43 and 44:
3 Model ComponentsThis chapter intr
Page 45 and 46:
Table 4:CERT-RMM Components by Cate
Page 47 and 48:
Figure 15: A Specific Goal and Spec
Page 49 and 50:
Figure 19: Summary of Major Model C
Page 51 and 52:
Figure 20: Format of Model Componen
Page 53 and 54:
4 Model RelationshipsSuccessful pro
Page 55 and 56:
Figure 21: Relationships That Drive
Page 57 and 58:
Asset Resilience ManagementEnvironm
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Part Two: Process Institutionalizat
Page 65 and 66:
To reach a particular level, an org
Page 67 and 68:
perform in the future. In CERT-RMM,
Page 69 and 70:
names of the generic goals, except
Page 71 and 72:
Generic Practice Related Process Ar
Page 73 and 74:
Such objectives may be high-level a
Page 75 and 76:
These four questions can be directl
Page 77 and 78:
The purpose of the establishing pha
Page 79 and 80:
CERT-RMM has a strong enterprise un
Page 81 and 82:
Communications (COMM)—to institut
Page 83 and 84:
Figure 31: Model Scope Options6.3.3
Page 85 and 86:
Figure 33: CERT-RMM Targeted Improv
Page 87 and 88:
Figure 34: Capability Level Ratings
Page 89 and 90:
If the immediate or long-term impro
Page 91 and 92:
ASSET DEFINITION AND MANAGEMENTEngi
Page 93 and 94:
Specific Practices by GoalADM:SG1 E
Page 95 and 96:
Facilities are any physical plant a
Page 97 and 98:
Information AssetsBecause informati
Page 99 and 100:
Ownership of assets typically varie
Page 101 and 102:
ADM:SG2.SP2 Analyze Asset-Service D
Page 103 and 104:
Organizational and operational cond
Page 105 and 106:
Subpractices1. Establish governance
Page 107 and 108:
ADM:GG2.GP3 Provide ResourcesProvid
Page 109 and 110:
Refer to the Human Resource Managem
Page 111 and 112:
ADM:GG2.GP6 Manage Work Product Con
Page 113 and 114:
ADM:GG2.GP8 Monitor and Control the
Page 115 and 116:
ADM:GG2.GP9 Objectively Evaluate Ad
Page 117 and 118:
ADM:GG3.GP2 Collect Improvement Inf
Page 119 and 120:
access controls current and reflect
Page 121 and 122:
COMMUNICATIONSEnterprisePurposeThe
Page 123 and 124:
COMM:SG2 Prepare for Communications
Page 125 and 126:
Related Process AreasA primary comp
Page 127 and 128:
CONTROLS MANAGEMENTEngineeringPurpo
Page 129 and 130:
The identification and implementati
Page 131 and 132:
ENVIRONMENTAL CONTROLOperationsPurp
Page 133 and 134:
EC:SG2 Protect Facility AssetsAdmin
Page 135 and 136:
The relationship between services a
Page 137 and 138:
EXTERNAL DEPENDENCIES MANAGEMENTOpe
Page 139 and 140:
Related Process AreasThe establishm
Page 141 and 142: EXD:SG4 Manage External Entity Perf
Page 143 and 144: Related Process AreasVisible and ac
Page 145 and 146: HUMAN RESOURCE MANAGEMENTEnterprise
Page 147 and 148: Specific Practices by GoalHRM:SG1 E
Page 149 and 150: IDENTITY MANAGEMENTOperationsPurpos
Page 151 and 152: Summary of Specific Goals and Pract
Page 153 and 154: and associated services and require
Page 155 and 156: IMC:SG2.SP4 Analyze and Triage Even
Page 157 and 158: KNOWLEDGE AND INFORMATION MANAGEMEN
Page 159 and 160: Specific Practices by GoalKIM:SG1 E
Page 161 and 162: MEASUREMENT AND ANALYSISProcessPurp
Page 163 and 164: MA:SG1.SP4 Specify Analysis Procedu
Page 165 and 166: supports and enables its monitoring
Page 167 and 168: ORGANIZATIONAL PROCESS DEFINITIONPr
Page 169 and 170: ORGANIZATIONAL PROCESS FOCUSProcess
Page 171 and 172: OPF:SG2.SP2 Implement Process Actio
Page 173 and 174: awareness program. Conduct Awarenes
Page 175 and 176: OTA:SG3.SP3 Establish Training Capa
Page 177 and 178: a steady stream of effective staff
Page 179 and 180: RISK MANAGEMENTEnterprisePurposeThe
Page 181 and 182: RISK:SG2 Establish Risk Parameters
Page 183 and 184: RESILIENCE REQUIREMENTS DEVELOPMENT
Page 185 and 186: egularly analyzing the requirements
Page 187 and 188: RESILIENCE REQUIREMENTS MANAGEMENTE
Page 189 and 190: RRM:SG1.SP4 Maintain Traceability o
Page 191: The functional aspects of software
Page 195 and 196: SERVICE CONTINUITYEngineeringPurpos
Page 197 and 198: Summary of Specific Goals and Pract
Page 199 and 200: SC:SG5 Exercise Service Continuity
Page 201 and 202: organization, the organization must
Page 203 and 204: TM:SG4.SP3 Perform Change Control a
Page 205 and 206: them to determine if breakdowns in
Page 207 and 208: Appendix A: Generic Goals and Pract
Page 209 and 210: Subpractices1. Establish governance
Page 211 and 212: GG2.GP3 Provide ResourcesProvide ad
Page 213 and 214: Subpractices1. Identify process ski
Page 215 and 216: GG2.GP8 Monitor and Control the Pro
Page 217 and 218: performing of the process can be ma
Page 219 and 220: Appendix B: Targeted Improvement Ro
Page 221 and 222: Required CERT-RMM Process AreasCate
Page 223 and 224: Process AreasRisk ManagementResilie
Page 225 and 226: Glossary of TermsThis document cont
Page 227 and 228: Asset-level resilience requirements
Page 229 and 230: Communications stakeholderA person
Page 231 and 232: Critical success factorsThe key are
Page 233 and 234: External dependencyAn external depe
Page 235 and 236: Identity registrationThe process of
Page 237 and 238: Key control indicatorsOrganizationa
Page 239 and 240: Operational riskThe potential impac
Page 241 and 242: PeopleAll staff, both internal and
Page 243 and 244:
ProvisioningThe process of assignin
Page 245 and 246:
Resilient Technical Solution Engine
Page 247 and 248:
SensitivityA measure of the degree
Page 249 and 250:
Technical controlA type of technica
Page 251 and 252:
Acronyms and InitialismsADMAsset De
Page 253 and 254:
EUDPDEuropean Union Data Protection
Page 255 and 256:
OPFOrganizational Process Focus (pr
Page 257 and 258:
ReferencesURLs are valid as of the
Page 259:
REPORT DOCUMENTATION PAGEForm Appro
show all

CERT Resilience Management Model, Version 1.0

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?