Hugging Face's logo

Datasets:
leeroy-jankins
/
DoD-Instruction-8500-01-Cybersecurity

Tasks:
Question Answering
Text Generation
Document Question Answering
Modalities:
Document
Text
Languages:
English
Tags:
department-of-defense
cybersecurity
risk-management-framework
information-security
dodin
cyberspace-defense
License:
Dataset card Data Studio Files
xet
 Community
Dataset Preview
Duplicate
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed because of a cast error
Error code:   DatasetGenerationCastError
Exception:    DatasetGenerationCastError
Message:      An error occurred while generating the dataset

All the data files must have the same columns, but at some point there are 5 new columns ({'Character Count', 'Unnamed: 0', 'Token Count', 'Chunk ID', 'Chunk Text'}) and 5 missing columns ({'ID', 'Question', 'User', 'Answer', 'Agent'}).

This happened while the csv dataset builder was generating data using

hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity/chunks/DoD Instruction 8500.01 Cybersecurity.csv (at revision a9a87ebd200b8cee2c7d6a56c2a50254463a9371), ['hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity@a9a87ebd200b8cee2c7d6a56c2a50254463a9371/DoD Instruction 8500.01 Cybersecurity.csv', 'hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity@a9a87ebd200b8cee2c7d6a56c2a50254463a9371/chunks/DoD Instruction 8500.01 Cybersecurity.csv']

Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1837, in _prepare_split_single
                  writer.write_table(table)
                  ~~~~~~~~~~~~~~~~~~^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 765, in write_table
                  self._write_table(pa_table, writer_batch_size=writer_batch_size)
                  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 773, in _write_table
                  pa_table = table_cast(pa_table, self._schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2369, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2297, in cast_table_to_schema
                  raise CastError(
                  ...<3 lines>...
                  )
              datasets.table.CastError: Couldn't cast
              Unnamed: 0: int64
              Chunk ID: int64
              Chunk Text: string
              Token Count: int64
              Character Count: int64
              -- schema metadata --
              pandas: '{"index_columns": [{"kind": "range", "name": null, "start": 0, "' + 874
              to
              {'ID': Value('int64'), 'User': Value('string'), 'Question': Value('string'), 'Agent': Value('string'), 'Answer': Value('string')}
              because column names don't match
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
                  parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
                                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      builder, max_dataset_size_bytes=max_dataset_size_bytes
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
                  builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
                  ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1683, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~^
                      gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  ):
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1839, in _prepare_split_single
                  raise DatasetGenerationCastError.from_cast_error(
                  ...<4 lines>...
                  )
              datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
              
              All the data files must have the same columns, but at some point there are 5 new columns ({'Character Count', 'Unnamed: 0', 'Token Count', 'Chunk ID', 'Chunk Text'}) and 5 missing columns ({'ID', 'Question', 'User', 'Answer', 'Agent'}).
              
              This happened while the csv dataset builder was generating data using
              
              hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity/chunks/DoD Instruction 8500.01 Cybersecurity.csv (at revision a9a87ebd200b8cee2c7d6a56c2a50254463a9371), ['hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity@a9a87ebd200b8cee2c7d6a56c2a50254463a9371/DoD Instruction 8500.01 Cybersecurity.csv', 'hf://datasets/leeroy-jankins/DoD-Instruction-8500-01-Cybersecurity@a9a87ebd200b8cee2c7d6a56c2a50254463a9371/chunks/DoD Instruction 8500.01 Cybersecurity.csv']
              
              Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

ID
int64
User
string
Question
string
Agent
string
Answer
string
1
User
What is the principal purpose of the Department of Defense cybersecurity policy?
Agent
The policy establishes a Department-wide cybersecurity program to protect and defend DoD information and information technology. It replaces the former information-assurance framework with an integrated cybersecurity model. The program governs risk management, resilience, system authorization, workforce responsibilitie...
2
User
Why did the Department replace the term “information assurance” with “cybersecurity”?
Agent
The instruction adopts the term “cybersecurity” from national cybersecurity policy. The change reflects a broader focus that includes protection, defense, threat response, resilience, and recovery rather than only assurance controls. It also aligns Department terminology with contemporary national-security and cyberspa...
3
User
Which major governance positions are established or continued by the cybersecurity program?
Agent
The policy establishes the positions of DoD Principal Authorizing Official and DoD Senior Information Security Officer. It also continues the DoD Information Security Risk Management Committee. These positions and bodies support strategic governance, risk acceptance, policy implementation, and enterprise oversight. Tog...
4
User
Which organizations are subject to the Department’s cybersecurity requirements?
Agent
The requirements apply to the Office of the Secretary of Defense, the Military Departments, the Joint Staff, and the Combatant Commands. They also apply to the DoD Inspector General, Defense Agencies, DoD Field Activities, and all other DoD organizational entities. These organizations are collectively treated as DoD Co...
5
User
What categories of technology and information fall within the policy’s scope?
Agent
The policy applies to all DoD information technology and all DoD information in electronic form. It also applies to special-access-program IT, except for SAP information systems handling sensitive compartmented information. The scope includes information systems, platform IT, IT services, and IT products. This ensures ...
6
User
How does the policy preserve the Director of National Intelligence’s authority?
Agent
The instruction does not alter or supersede the Director of National Intelligence’s authorities regarding protection of sensitive compartmented information. Existing intelligence-community policies remain controlling where applicable. This preserves the legal and policy framework governing SCI. DoD cybersecurity requir...
7
User
What does the Department’s multi-tiered cybersecurity risk-management process protect?
Agent
The process protects United States interests, DoD operational capabilities, individuals, organizations, information, and assets. It operates from the DoD Information Enterprise level through the Component level and down to the information-system level. Risk decisions at each tier influence and inform the others. The ap...
8
User
Why must supply-chain and global-sourcing risks be considered in cybersecurity decisions?
Agent
DoD systems may depend on globally sourced hardware, software, components, and services. Those supply chains can introduce malicious components, counterfeit products, design weaknesses, or compromised dependencies. Adversaries may exploit such vulnerabilities to disrupt military, intelligence, or business operations. C...
9
User
Why must every DoD IT asset be assigned to a Component cybersecurity program?
Agent
Assignment ensures that an accountable organization manages the asset’s risk. The Component program must apply controls proportionate to mission importance and the value of affected information or assets. Without such assignment, responsibility for authorization, monitoring, incident response, and compliance could beco...
10
User
Why must cybersecurity risk management begin early in acquisition?
Agent
Early integration allows security requirements to influence design, architecture, engineering, testing, and procurement. Delaying cybersecurity until fielding often makes corrective action more expensive and time-consuming. Late changes can also degrade system performance or delay deployment. Early risk management ther...
11
User
How does cybersecurity reciprocity reduce unnecessary effort?
Agent
Reciprocity allows one authorizing official to rely on credible security evidence produced by another organization. This reduces duplicate testing, assessment, and documentation. It depends on transparency regarding the system’s security posture and authorization package. Sharing sufficient evidence allows other organi...
12
User
What is the objective of operational resilience?
Agent
Operational resilience ensures that DoD missions can continue despite cyber incidents, degraded systems, or loss of information resources. It requires trustworthy resources, mission readiness for degradation, and network operations capable of prevailing during adverse events. Systems must be able to resist, absorb, rec...
13
User
Why must cybersecurity posture be visible across the DoD Information Enterprise?
Agent
Visibility allows mission owners, system operators, and enterprise leaders to understand current risk and operational conditions. It supports correlation of information from individual devices through systems of systems. Shared awareness improves prioritization, incident response, and risk decisions. Without visibility...
14
User
What role does automated reconfiguration and recovery play in resilience?
Agent
Automated capabilities can reconfigure, optimize, defend, and recover systems with limited human intervention. This can reduce response time during fast-moving cyber events. Attempts to reconfigure or recover should produce an auditable incident trail. Automation therefore supports both resilience and accountability.
15
User
Why must cybersecurity be integrated into system life cycles and IT portfolios?
Agent
Cybersecurity affects design, acquisition, testing, operation, sustainment, and replacement. Treating it as a separate activity can create gaps between mission planning and technical implementation. Visible integration allows leaders to evaluate cybersecurity alongside cost, schedule, performance, and operational readi...
16
User
How does standards-based interoperability support cybersecurity?
Agent
Common standards allow cybersecurity products and systems to exchange data, policies, and security information. Standards reduce incompatibility among tools such as firewalls, scanners, and intrusion-detection systems. They also support faster automation and enterprise-wide analysis. Interoperability must remain consis...
17
User
Why must interconnected systems manage shared risk?
Agent
A secure system can be undermined by a vulnerable system to which it is connected. Interconnections may create pathways for malware, unauthorized access, or data compromise. Managing shared risk requires evaluation of both sides of the connection and their combined security posture. The objective is to prevent one syst...
18
User
What actions are included in cyberspace defense?
Agent
Cyberspace defense includes detecting, characterizing, countering, and mitigating threats. It also includes restoring systems to a secure configuration after compromise or attempted compromise. Threats may include malware, unauthorized activity, vulnerabilities, or other hostile actions. These activities are conducted ...
19
User
How is cybersecurity performance connected to mission outcomes?
Agent
Cybersecurity performance is measured according to its contribution to strategic goals and mission results. Metrics should not focus solely on technical activity counts. They should help leaders determine whether cybersecurity enables reliable operations and protects mission-critical functions. Data are collected throu...
20
User
Why does the Department emphasize standardized tools, methods, and processes?
Agent
Standardization reduces duplicate development and acquisition costs. It also promotes verified, mature solutions that can be reused across Components. Common methods improve consistency in assessment, monitoring, reporting, and remediation. The approach allows resources to be focused on enterprise capability rather tha...
21
User
How must electronic DoD information be protected?
Agent
Electronic information must receive confidentiality, integrity, and availability protections appropriate to its importance. The protection level must balance information sharing with information security. Classified information, controlled unclassified information, personally identifiable information, and other sensiti...
22
User
What is the purpose of identity assurance in DoD systems?
Agent
Identity assurance provides strong identification and authentication of users and other entities. It is intended to eliminate anonymity within DoD information systems and platform IT systems. Access and behavior should be visible, traceable, and available for monitoring and investigation. Identity assurance also protec...
23
User
Why does the Department require a DoD-wide public-key infrastructure?
Agent
A common PKI supports digital signatures, encryption, identity authentication, and trust across the Department. It provides a scalable way to bind digital credentials to approved identities. Central management improves interoperability and consistent certificate policy. PKI is a core mechanism for strong identity assur...
24
User
How are biometrics incorporated into identity assurance?
Agent
Biometrics may support identification and authentication when used under applicable DoD biometrics policy. Their use must be governed consistently with identity-assurance requirements. Biometric information must be protected for integrity, privacy, authenticity, and availability. The technology supplements rather than ...
25
User
What lifecycle requirements apply to IT that handles DoD information?
Agent
Such IT must be acquired, configured, operated, maintained, and disposed of consistently with cybersecurity policy, standards, and architectures. Requirements must be addressed during design, development, testing, integration, operation, upgrade, and replacement. Risks created by faulty design, configuration, global so...
26
User
Why must qualified cybersecurity personnel participate in every phase of system development?
Agent
Cybersecurity decisions made during early design and acquisition can have long-term consequences. Qualified personnel help identify requirements, vulnerabilities, controls, and testing needs before they become costly to change. Their participation improves the maturity of security engineering across the lifecycle. It a...
27
User
How must DoD information on mission-partner systems be protected?
Agent
DoD-originated or DoD-provided information must receive adequate safeguards even when it resides on a partner system. Formal agreements must document the required protection levels. The agreement should address risk, access, handling, and operational responsibilities. Partner ownership does not reduce DoD’s obligation ...
28
User
What is the DoD Chief Information Officer’s overarching cybersecurity role?
Agent
The DoD CIO monitors, evaluates, and advises the Secretary of Defense on cybersecurity activities. The office establishes policy, oversees implementation, appoints key officials, and coordinates with other senior leaders. It also advocates resources and develops enterprise governance mechanisms. This role provides Depa...
29
User
Why does the DoD CIO coordinate with the intelligence community CIO?
Agent
Coordination supports protection of intelligence-community information within DoD systems. It also promotes reciprocity between DoD and intelligence authorization processes. Alignment reduces conflicting cybersecurity requirements across communities. Continuous coordination helps maintain consistent risk management for...
30
User
Why must cybersecurity be coordinated with personnel, physical, industrial, information, and operations security?
Agent
Cybersecurity risks often overlap with other security disciplines. A technical vulnerability may involve an insider, contractor, facility, classified document, or operational indicator. Coordination creates a unified security posture rather than isolated programs. It also improves inspections, metrics, and incident res...
31
User
What resource responsibilities does the DoD CIO exercise?
Agent
The DoD CIO coordinates and advocates funding for enterprise cybersecurity solutions. The office oversees appropriations allocated to the cybersecurity program. It also maintains a Defense-wide view of cybersecurity resources for national, joint, organizational, and Component planning. This supports strategic prioritiz...
32
User
What role does the DoD CIO perform in cross-domain solutions?
Agent
The DoD CIO establishes policy for lifecycle management of cross-domain solutions. This includes governance of development, approval, operation, and sustainment. Cross-domain systems transfer information between security domains and therefore require specialized controls. Enterprise policy reduces inconsistent or unsaf...
33
User
Why is continuous-monitoring policy developed at the Department level?
Agent
Enterprise policy creates common expectations for data collection, reporting, risk assessment, and situational awareness. NSA, DISA, and Components contribute technical and operational input. A common framework allows data to be aggregated and compared across organizations. This supports timely enterprise risk decision...
34
User
What is the purpose of the Defense Security/Cybersecurity Authorization Working Group?
Agent
The group supports cybersecurity authorization and risk governance across the Department. Its chair is appointed by the DoD CIO. It assists the DoD Information Security Risk Management Committee. The working group provides technical and operational coordination for difficult or enterprise-level risk issues.
35
User
Why must the DoD CIO conduct annual Component cybersecurity assessments?
Agent
Annual assessments provide oversight of Component program effectiveness and compliance. They support statutory reporting and enterprise risk awareness. The results can reveal recurring weaknesses, capability gaps, and resource needs. They also promote accountability among Component leadership.
36
User
What cybersecurity responsibilities belong to the Director of DISA?
Agent
DISA develops, implements, and manages cybersecurity for the Defense Information Systems Network in coordination with U.S. Cyber Command. It produces technical guidance, supports connection approval, develops enterprise solutions, and operates cybersecurity repositories. DISA also conducts readiness inspections and ope...
37
User
What are control correlation identifiers?
Agent
A control correlation identifier breaks a security control into a single, actionable, measurable statement. CCIs help translate broad control requirements into specific implementation and assessment items. They support automation, tracking, and standardized compliance evaluation. DISA develops and maintains them with s...
38
User
What is the purpose of security requirements guides and security technical implementation guides?
Agent
SRGs organize security requirements for technology areas at different levels of specificity. STIGs provide implementation guidance for particular products and versions. They translate policy and security controls into concrete configuration requirements. Compliance helps create consistent and secure configurations acro...
39
User
Why does DISA maintain the DoD Cyber Exchange?
Agent
The DoD Cyber Exchange serves as a knowledge repository for cybersecurity policy, guidance, tools, and information. It provides Components with access to common resources such as training and configuration materials. Central publication promotes consistency and reuse. It also reduces the need for organizations to maint...
40
User
What connection responsibilities does DISA exercise?
Agent
DISA oversees and maintains connection approval for the DISN. This includes NIPRNet, SIPRNet, cross-domain connections, ports, protocols, services, and unified-capabilities requirements. Coordination may involve the DSAWG and the DoD risk committee. The process ensures that connections do not introduce unacceptable ent...
41
User
How does DISA support multinational cybersecurity cooperation?
Agent
DISA facilitates information sharing with eligible foreign partners and supports international cybersecurity agreements. It also supports training, exercises, workforce development, and network evaluation. These activities help build partner capacity and improve collective cyber awareness. All cooperation remains subje...
42
User
Why does DISA conduct command cyber-readiness inspections?
Agent
Inspections assess whether networks and systems comply with cybersecurity policy and operational requirements. They provide commanders with a systemic view of readiness and risk. Results support remediation and U.S. Cyber Command oversight. Inspections also help unify cybersecurity implementation across Components.
43
User
How does acquisition leadership integrate cybersecurity into defense programs?
Agent
Acquisition leadership incorporates cybersecurity into policy, regulations, research, systems engineering, testing, and program protection. It ensures that acquisition programs plan, implement, test, and evaluate security throughout the lifecycle. Platform IT must be designated, categorized, and assigned authorization ...
44
User
Why must developmental testing include cybersecurity?
Agent
Developmental testing identifies design, implementation, integration, and resilience weaknesses before operational fielding. Adequate testing must be planned, resourced, documented, and executable in time to inform program decisions. It also supports interoperability and systems-engineering reviews. Early discovery red...
45
User
What is the role of the Director of Operational Test and Evaluation in cybersecurity?
Agent
The Director establishes policy for cybersecurity testing during operational evaluation. The office conducts or oversees independent assessments of systems under acquisition. Findings are reported through the acquisition process and influence fielding decisions. Operational testing evaluates how systems perform against...
46
User
Why must operational testing include independent penetration and exploitation testing?
Agent
Independent testing provides a threat-representative evaluation of the complete system’s defenses. It examines not only the system but also protections provided by cybersecurity service providers. Such testing helps reveal vulnerabilities that routine compliance reviews may miss. It must be planned and funded in formal...
47
User
How does policy leadership support international cybersecurity agreements?
Agent
Policy leadership aligns cybersecurity agreements with broader cyberspace and foreign-disclosure policy. It coordinates negotiation, implementation, and disclosure issues with the DoD CIO. This helps ensure that international cooperation supports national objectives. It also prevents technical arrangements from conflic...
48
User
What cybersecurity workforce responsibility belongs to Personnel and Readiness leadership?
Agent
Personnel and Readiness supports effective manning, management, qualification, and readiness assessment of the cybersecurity workforce. It coordinates personnel identity and cybersecurity workforce policies with the DoD CIO. The goal is to maintain a professional workforce with appropriate screening, training, and qual...
49
User
What cybersecurity responsibilities belong to intelligence leadership?
Agent
Intelligence leadership coordinates cybersecurity with personnel, physical, industrial, information, and operations security. It also participates in international cybersecurity strategy and agreements. The office appoints the principal authorizing official for the DoD portion of the Intelligence Mission Area. This pre...
50
User
What role does the National Security Agency perform in DoD cybersecurity?
Agent
NSA provides cybersecurity architecture, cryptography, PKI, systems-security engineering, and security-evaluation expertise. It supports threat and vulnerability assessment and helps develop technical specifications, SRGs, and STIGs. NSA also manages key infrastructure and approves cryptography for classified informati...
51
User
Why does NSA evaluate information-assurance and cybersecurity-enabled products?
Agent
Evaluation determines whether products provide reliable security functions and meet national policy requirements. Products may include operating systems, firewalls, routers, or other technologies with security capabilities. Central validation reduces reliance on unverified claims. It also supports consistent acquisitio...
52
User
What role does systems security engineering play in cybersecurity?
Agent
Systems security engineering identifies protection needs and integrates controls into system architecture and design. It supports implementation, testing, modification, and lifecycle risk management. SSE helps ensure that security is engineered into the system rather than added after development. It also supports trust...
53
User
Why must cryptographic algorithms protecting classified information receive NSA approval?
Agent
Classified information requires cryptography that meets national-security standards. NSA has specialized authority and expertise to evaluate algorithms and implementations. Approval reduces the risk of weak or improperly applied cryptographic protection. It also ensures compatibility with national cryptographic policy.
54
User
How are mobile-code technologies governed?
Agent
Each mobile-code technology must undergo a risk assessment. It is assigned to a risk category based on its functionality, access, and potential impact. Use is regulated according to the risk it poses to DoD operations and systems. Technical countermeasures may be developed for specific implementations.
55
User
What contractor-security role belongs to the Defense Counterintelligence and Security Agency?
Agent
DCSA monitors and oversees information-system security practices of contractors and vendors processing classified DoD information. It applies industrial-security and cybersecurity requirements. This oversight helps protect classified information outside government-operated systems. Contractor environments remain subjec...
56
User
What cybersecurity role does the Defense Intelligence Agency perform?
Agent
DIA provides finished intelligence and threat assessments supporting cybersecurity activities. It also develops and manages cybersecurity for non-cryptographic SCI systems. This includes the DoD intelligence information environment and the Joint Worldwide Intelligence Communications System. DIA’s role complements NSA’s...
57
User
Why must DoD Component heads appoint authorizing officials?
Agent
Every DoD information system and platform IT system requires an accountable official to make authorization decisions. The AO formally accepts responsibility for operating the system at an acceptable level of risk. Appointment ensures that risk acceptance is not left to technical personnel without authority. It also cre...
58
User
Why must platform IT systems be centrally identified and registered?
Agent
Platform IT may exist in weapons, facilities, vehicles, medical devices, utilities, and industrial-control environments. Central identification ensures that such systems are not overlooked by conventional IT governance. Registration supports categorization, authorization, monitoring, and lifecycle management. It also h...
59
User
How do trusted systems and networks practices support acquisition?
Agent
TSN practices address supply-chain and mission-critical-function risks. They use criticality analysis, threat-informed acquisition, engineering mitigations, and procurement tools. The practices should begin early and continue through sustainment and replacement. Their purpose is to protect critical components from mali...
60
User
What incident-response capabilities must Components provide?
Agent
Components must be able to mitigate vulnerabilities, respond to incidents, limit damage, restore service, and support cyberspace defense. They must collect audit data for technical analysis and investigations. Reporting procedures must address classified compromise, CUI disclosure, contractor incidents, and privacy bre...
61
User
Why must contracts contain specific cybersecurity requirements?
Agent
Contractors and partners may process DoD information or operate supporting IT. Clear contractual language defines required controls, reporting, access, and protection responsibilities. Without explicit requirements, enforcement and accountability may be weakened. Contract provisions extend DoD cybersecurity expectation...
62
User
Why must personnel with access to DoD IT be appropriately cleared and qualified?
Agent
Access to systems and information can create significant mission and security risk. Clearance and qualification requirements help ensure trustworthiness, competence, and legal eligibility. Different information categories may require different access determinations. The requirement applies to both privileged and ordina...
63
User
What written-assignment requirements apply to cybersecurity positions?
Agent
Personnel occupying cybersecurity positions must be assigned in writing. Their position designation, duties, and responsibilities must be documented. They must meet training, qualification, suitability, and fitness requirements. Written assignment improves accountability and workforce management.
64
User
Why must Components supplement enterprise cybersecurity-awareness training?
Agent
Enterprise training provides a common baseline for all users. Components may face specialized missions, systems, threats, or procedures requiring additional instruction. Supplemental training reinforces enterprise objectives and addresses local risks. This ensures that awareness is relevant to the user’s actual environ...
65
User
What privacy and monitoring notices must users receive?
Agent
Individuals accessing DoD-controlled systems must receive notice of applicable privacy rights and monitoring policies. Standard notice-and-consent banners are displayed at logon. User agreements must also include mandatory consent provisions. These notices establish expectations and support lawful monitoring.
66
User
How must cybersecurity solutions account for individuals with disabilities?
Agent
Security measures must not unnecessarily restrict assistive technology. They should also preserve access to information and data by individuals with disabilities. Cybersecurity implementation must comply with applicable accessibility law. Security and accessibility should be designed together rather than treated as inc...
67
User
Why do Components conduct Blue Team, Red Team, vulnerability, and intrusion assessments?
Agent
These activities provide different perspectives on the security posture of systems and enclaves. Blue Teams evaluate vulnerabilities and defensive readiness, while Red Teams emulate adversarial activity. Intrusion assessments and inspections reveal weaknesses in controls and operations. Together they provide a systemic...
68
User
Why must cybersecurity testing be integrated with interoperability and other functional testing?
Agent
A system can be secure yet fail operationally if cybersecurity prevents required mission interaction. Conversely, interoperable systems may expose unacceptable vulnerabilities. Integrated testing evaluates the combined mission effect. Cybersecurity representatives therefore participate in planning, execution, and repor...
69
User
What system-reporting requirement applies to DoD Components?
Agent
All systems must be reported in the Enterprise Mission Assurance Support Service or Enterprise Reporting System. Components using alternate tools must ensure required data can be imported regularly into ERS. New systems are reported at the beginning of the development lifecycle. This creates enterprise visibility into ...
70
User
How are exceptions to STIGs and security guides handled?
Agent
All DoD IT must comply with applicable STIGs, SRGs, and security-configuration guides. Any exception must be documented and approved by the responsible authorizing official. The exception should reflect a reasoned risk decision rather than informal noncompliance. This preserves accountability for deviations.
71
User
Why are DISA cross-domain services preferred?
Agent
Enterprise services provide standardized security, approval, monitoring, and sustainment. Using them reduces duplication and the proliferation of local cross-domain solutions. They also support consistent lifecycle governance. Components may address unique requirements, but enterprise services are the preferred approac...
72
User
What accountability applies to commanders, system owners, security managers, and administrators?
Agent
These personnel are responsible for implementing applicable cybersecurity requirements. Privileged personnel must be qualified and formally accept their responsibilities. Leaders may face administrative or judicial consequences for knowingly, willfully, or negligently placing DoD information at risk. Accountability ext...
73
User
Why must TEMPEST countermeasures be funded and implemented?
Agent
Compromising emanations may allow sensitive information to be intercepted from electronic equipment. National policy and technical guidance establish when countermeasures are required. Components must fund and implement those protections. TEMPEST is therefore treated as part of the broader cybersecurity and information...
74
User
What cybersecurity responsibilities belong to the Chairman of the Joint Chiefs of Staff?
Agent
The Chairman advises on joint military cybersecurity requirements and supports international activities. The office develops joint and combined cybersecurity doctrine and guidance. It also appoints the principal authorizing official for the Warfighting Mission Area. These responsibilities connect cybersecurity governan...
75
User
What authority does U.S. Cyber Command exercise over DODIN operations and defense?
Agent
U.S. Cyber Command coordinates and directs DODIN operations and defense under the Unified Command Plan. It issues orders and directives addressing cybersecurity and cyberspace defense. Actions affecting multiple Components or areas outside a network owner’s authority are centrally coordinated. This provides unity of co...
76
User
Why does U.S. Cyber Command chair the DoD risk committee?
Agent
The committee manages enterprise cybersecurity risk from a strategic perspective. U.S. Cyber Command’s operational view helps connect risk decisions with current threats and DODIN defense. Chairing the committee supports coordination among mission-area authorizing officials and major stakeholders. It also aligns strate...
77
User
What is the operational vision of the DoD cybersecurity program?
Agent
DoD missions should continue under any cyber condition. Weapon-system and platform IT should perform as designed, and the information enterprise should act collectively in its own defense. DoD should retain access to information and command-and-control channels while denying adversaries comparable access. The enterpris...
78
User
How is cybersecurity risk related to acquisition risk?
Agent
Cybersecurity risk is a subset of broader acquisition risk. It interacts with cost, schedule, performance, logistics, and supply-chain concerns. A cyber weakness may affect fielding, sustainment, operational effectiveness, or mission success. Cybersecurity must therefore be managed with other program risks rather than ...
79
User
What are the three tiers of the Department’s risk-management model?
Agent
Tier 1 addresses organization-level risk. Tier 2 addresses mission and business-process risk. Tier 3 addresses information-system and platform-system risk. Decisions and information flow between the tiers through feedback, communication, and continuous improvement.
80
User
What governance occurs at Tier 1?
Agent
Tier 1 establishes organization-wide security governance and strategic risk direction. It aligns security strategies with mission objectives, laws, policies, and internal controls. The DoD Information Security Risk Management Committee provides the principal Tier 1 governance. Decisions at lower tiers inform and influe...
81
User
What governance occurs at Tier 2?
Agent
Tier 2 manages risk from the mission and business-process perspective. It is guided by organization-level risk decisions and informed by system-level risk. Principal authorizing officials govern their respective mission areas at this tier. The focus is aligning system protection with mission and business requirements.
82
User
What activities occur at Tier 3?
Agent
Tier 3 applies security protections to individual information systems and platform IT systems. Security controls are selected, implemented, assessed, and monitored at this level. Common-control providers, system managers, and program managers implement controls. Authorizing officials make risk-based authorization decis...
83
User
Why does the three-tier model require feedback between levels?
Agent
Strategic decisions need information about actual system vulnerabilities and mission impacts. System-level actions also need guidance from organizational risk tolerance and mission priorities. Feedback creates traceability and continuous improvement. It prevents tactical decisions from becoming disconnected from enterp...
84
User
What are the six steps of the Risk Management Framework?
Agent
The steps are categorizing the system, selecting security controls, implementing controls, assessing controls, authorizing the system, and monitoring controls. The process integrates security and risk management into the system lifecycle. It applies to DoD information systems and platform IT systems. The framework prov...
85
User
How may risk assessments be tailored?
Agent
The depth of a risk assessment may reflect resource constraints and the availability of threat or vulnerability data. However, all required risk factors must still be considered. Any tailoring must be clearly explained in the assessment report. This allows authorizing officials to understand the reliability and limitat...
86
User
Why must DoD use common risk factors across Components?
Agent
Common factors improve reciprocity and comparability. They allow authorizing officials to understand assessments produced by other organizations. Standardization also supports enterprise aggregation and risk analysis. Without common factors, assessments may not be credible or reusable across organizational boundaries.
87
User
How are security controls selected for DoD systems?
Agent
Systems are categorized according to applicable national-security categorization guidance. They then implement corresponding controls from the NIST control catalog. DoD-specific values, guidance, and validation procedures supplement the national controls. Selection reflects the system’s impact level, mission, and risk.
88
User
Why do both national-security and non-national-security systems use the same control catalog?
Agent
A common catalog creates consistency across the Department. It allows DoD-specific implementation to be applied regardless of system designation. National-security overlays and policies may add specialized requirements. The common foundation supports reciprocity, assessment, and enterprise governance.
89
User
How does the Knowledge Service support the Risk Management Framework?
Agent
The Knowledge Service publishes DoD-specific control values, implementation guidance, assessment procedures, templates, and related resources. It provides a common source for Components and authorizing officials. Updates can reflect changes in NIST, CNSS, and DoD policy. The repository supports consistent RMF execution...
90
User
Why is transparency essential to cybersecurity reciprocity?
Agent
Reciprocity depends on another organization being able to evaluate existing security evidence. If documentation is incomplete or inaccessible, the receiving authorizing official cannot make a credible risk decision. Sharing authorization packages reduces redundant work. Transparency therefore converts prior assessment ...
91
User
What three conditions are required for operational resilience?
Agent
Information resources must be trustworthy. Missions must be prepared for degradation or loss of those resources. Network operations must have the means to prevail during adverse events. All three conditions are necessary because secure technology alone cannot guarantee mission continuation.
92
User
How do trusted-systems-and-networks practices protect mission-critical functions?
Agent
TSN practices identify critical components and functions. They apply threat-informed acquisition, criticality analysis, engineering mitigation, and supply-chain controls. The practices continue through acquisition, sustainment, replacement, and integration. Their purpose is to preserve the integrity of critical technol...
93
User
Why must systems be exercised under realistic cyber conditions?
Agent
Realistic exercises reveal whether missions can continue when systems or connectivity fail. They test workarounds, fallbacks, resource allocation, recovery, and decision making. Routine exercises may not reveal weaknesses that appear under hostile conditions. The results inform readiness and resilience improvements.
94
User
What operational capabilities are required during loss of information resources?
Agent
Organizations must be able to operate during significant resource or connectivity loss. They should dynamically allocate remaining resources to sustain mission operations. They must also restore resources quickly to a trusted state. Recovery must occur while continuing to support ongoing missions where possible.
95
User
How is information protected during transmission?
Agent
DoD uses communications-security measures and transmission-security controls. COMSEC monitoring verifies compliance and proper use. TEMPEST countermeasures address compromising emanations where required. Together these protections preserve trust in information while it moves across communications systems.
96
User
Why is automation emphasized in secure configuration and continuous monitoring?
Agent
Automation improves speed, consistency, scale, and repeatability. It can detect deviations, collect status data, support active defense, and accelerate incident reporting. Automated processes also reduce manual errors. Human oversight remains necessary, but automation enables enterprise-level responsiveness.
97
User
What is the purpose of a net-centric cybersecurity model?
Agent
A net-centric model allows people, systems, services, and platforms to discover and connect with one another. Cybersecurity capabilities must operate in flexible combinations as missions change. Shared policies and data enable rapid enterprise response. The model seeks readiness without being constrained by geographic ...
98
User
What are semantic, technical, and policy interoperability?
Agent
Semantic interoperability ensures that exchanged data are understood as intended. Technical interoperability enables technologies to communicate through common interfaces. Policy interoperability aligns business processes governing transmission, receipt, and acceptance. Effective cybersecurity integration requires all ...
99
User
Why are cybersecurity knowledge repositories described as community memory?
Agent
They preserve standards, benchmarks, templates, tools, lessons, and best practices. This prevents valuable knowledge from being lost or repeatedly recreated. Repositories also support policy and process interoperability. Users can consult them to answer questions and implement consistent practices.
100
User
When may a Component take cyberspace defensive action independently?
Agent
A Component that owns or operates a network may generally defend it within its area of responsibility. Independent action should not compromise operations outside that responsibility. Actions affecting multiple Components or external areas require U.S. Cyber Command coordination. This balances local responsiveness with...
End of preview.
DoD Cybersecurity Question-Answer Dataset

🛡️ DoD Cybersecurity Question-Answer Dataset

Source: U.S. Government Records Language

  • Source: DoD Instruction 8500.01
  • Source Effective Date: March 14, 2014
  • Change Incorporated: Change 1, effective October 7, 2019
  • Source Organization: Office of the DoD Chief Information Officer
  • Source Ownership: United States Department of Defense

📋 Overview

Dataset Summary

The DoD Cybersecurity Question-Answer Dataset is a structured, document-grounded natural-language dataset derived from DoD Instruction 8500.01, “Cybersecurity,” effective March 14, 2014, incorporating Change 1 effective October 7, 2019.

The source establishes the Department of Defense cybersecurity program and provides the policy framework for protecting and defending DoD information, information technology, information systems, platform information technology, IT services, IT products, and the Department of Defense Information Network.

The dataset contains substantive questions and detailed answers addressing:

  • Department-wide cybersecurity policy
  • Cybersecurity governance
  • Multi-tiered risk management
  • Risk Management Framework implementation
  • Information-system authorization
  • Platform IT and platform IT systems
  • Information systems, enclaves, and major applications
  • IT services and products
  • Operational resilience
  • Cyberspace defense
  • DODIN operations
  • Continuous monitoring
  • Cybersecurity testing and inspections
  • Cybersecurity reciprocity
  • Supply-chain risk
  • Trusted systems and networks
  • Systems-security engineering
  • Identity assurance
  • Public-key infrastructure
  • Biometrics
  • Information protection
  • Controlled unclassified information
  • Classified information
  • Personally identifiable information
  • Mission-partner systems
  • International cybersecurity agreements
  • Cybersecurity workforce requirements
  • Contractor cybersecurity
  • Acquisition, developmental testing, and operational testing
  • Security controls
  • Security Technical Implementation Guides
  • Security Requirements Guides
  • Control Correlation Identifiers
  • Ports, protocols, and services
  • Cross-domain services
  • Communications security
  • TEMPEST
  • Incident response
  • Vulnerability management
  • Information spillage
  • Media sanitization
  • User responsibilities
  • Privileged-user responsibilities
  • Authorizing officials
  • Principal Authorizing Officials
  • Information-system owners
  • Information-system security managers
  • Information-system security officers

The records are intended to support retrieval-augmented generation, closed-domain question answering, cybersecurity-policy education, regulatory grounding, risk-management training, system-authorization analysis, and domain adaptation for models working with DoD cybersecurity requirements.

Source Document

The dataset is derived from:

DoD Instruction 8500.01
Cybersecurity
Effective March 14, 2014
Incorporating Change 1, Effective October 7, 2019

The issuance:

  • Establishes the DoD cybersecurity program
  • Replaces the former information-assurance framework
  • Establishes the position of DoD Principal Authorizing Official
  • Establishes the position of DoD Senior Information Security Officer
  • Continues the DoD Information Security Risk Management Committee
  • Establishes a multi-tiered cybersecurity risk-management process
  • Requires assignment of DoD IT to Component cybersecurity programs
  • Integrates cybersecurity into acquisition and system lifecycles
  • Requires operational resilience
  • Establishes cybersecurity reciprocity
  • Requires visibility of cybersecurity posture
  • Establishes cyberspace-defense requirements
  • Establishes continuous-monitoring requirements
  • Establishes identity-assurance requirements
  • Establishes information-protection requirements
  • Establishes workforce qualification requirements
  • Establishes responsibilities for DoD senior officials and Components
  • Applies the Risk Management Framework to DoD information systems and platform IT systems
  • Establishes requirements for mission-partner systems
  • Establishes cybersecurity requirements for IT services and products
  • Establishes accountability for system owners, administrators, and users

The source is cleared for public release.

Source Version

Attribute Value
Issuance DoD Instruction 8500.01
Title Cybersecurity
Effective date March 14, 2014
Change incorporated Change 1
Change effective date October 7, 2019
Originating component Office of the DoD Chief Information Officer
Releasability Cleared for public release
Principal governance body DoD Information Security Risk Management Committee
Principal program official DoD Senior Information Security Officer
Principal system framework Risk Management Framework
Principal operational cyber authority Commander, U.S. Cyber Command
Enterprise network Department of Defense Information Network

Change 1

Change 1:

  • Updated organizational names and titles
  • Updated references and Internet addresses
  • Revised the description of cyberspace defense
  • Added cybersecurity scorecard-reporting requirements
  • Established a minimum moderate confidentiality-impact level for systems processing controlled unclassified information
  • Replaced legacy organization names with current designations, including U.S. Cyber Command and the Defense Counterintelligence and Security Agency
  • Made administrative and technical corrections

Dataset Scope

The dataset covers:

  • Cybersecurity
  • Information assurance
  • DoD Information Enterprise
  • Department of Defense Information Network
  • Cyberspace defense
  • DODIN operations
  • Operational resilience
  • Risk Management Framework
  • Cybersecurity risk management
  • Organization-level risk
  • Mission and business-process risk
  • System-level risk
  • Risk executive function
  • DoD Information Security Risk Management Committee
  • Defense Security/Cybersecurity Authorization Working Group
  • Principal Authorizing Officials
  • Authorizing officials
  • DoD Senior Information Security Officer
  • Component Senior Information Security Officers
  • Information-system owners
  • Information owners
  • Information stewards
  • Information-system security managers
  • Information-system security officers
  • Privileged users
  • Authorized users
  • Information systems
  • Enclaves
  • Major applications
  • Stand-alone systems
  • Platform information technology
  • Platform IT systems
  • IT services
  • IT products
  • Unified-capabilities products
  • Cross-domain services
  • National security systems
  • Security categorization
  • Security controls
  • Control baselines
  • Security-control enhancements
  • Overlays
  • Common controls
  • Control Correlation Identifiers
  • Security Requirements Guides
  • Security Technical Implementation Guides
  • Security Content Automation Protocol
  • Continuous monitoring
  • Penetration testing
  • Exploitation testing
  • Red Team assessments
  • Blue Team assessments
  • Cyber-readiness inspections
  • Vulnerability assessments
  • Incident response
  • Cybersecurity metrics
  • Cybersecurity scorecards
  • Cybersecurity reciprocity
  • Authorization packages
  • Supply-chain risk management
  • Trusted systems and networks
  • Criticality analysis
  • Program-protection planning
  • Systems-security engineering
  • Developmental testing
  • Operational testing
  • Identity assurance
  • Public-key infrastructure
  • Coalition PKI
  • Biometrics
  • Digital signatures
  • Encryption
  • Authentication
  • Person identities
  • Non-person identities
  • Controlled unclassified information
  • Classified information
  • Sensitive compartmented information
  • Personally identifiable information
  • Protected health information
  • Information markings
  • Metadata
  • Public-release review
  • Information spillage
  • Mission partners
  • DoD-partnered systems
  • Foreign access
  • International cybersecurity agreements
  • Cryptographic material
  • Contractor systems
  • Defense Industrial Base cybersecurity
  • Communications security
  • Transmission security
  • TEMPEST
  • Mobile code
  • Ports, protocols, and services
  • BIOS protection
  • Trusted platform modules
  • Media sanitization
  • Telework
  • Assistive technology
  • Cybersecurity workforce
  • User awareness
  • User agreements
  • Notice-and-consent banners

Applicability

The instruction applies to:

  • Office of the Secretary of Defense
  • Military Departments
  • Office of the Chairman of the Joint Chiefs of Staff
  • Joint Staff
  • Combatant Commands
  • Office of Inspector General of the Department of Defense
  • Defense Agencies
  • DoD Field Activities
  • Other organizational entities within the Department

These organizations are collectively referred to as DoD Components.

The policy applies to:

  • All DoD information technology
  • All DoD information in electronic form
  • DoD information systems
  • Platform information technology
  • Platform IT systems
  • IT services
  • IT products
  • Special-access-program IT, subject to stated exceptions

The instruction does not alter or supersede Director of National Intelligence authority concerning protection of sensitive compartmented information.

Cybersecurity Policy Framework

Mission Enablement

Cybersecurity is intended to enable DoD missions while protecting:

  • Operational capabilities
  • Information
  • Information systems
  • Platform systems
  • Organizations
  • Individuals
  • Assets
  • National interests

Security decisions must account for mission requirements, operational consequences, system dependencies, and organizational risk tolerance.

Multi-Tiered Risk Management

The Department uses a three-tier risk-management model.

Tier Focus
Tier 1 Organization-level cybersecurity governance and strategic risk
Tier 2 Mission and business-process risk
Tier 3 Information-system and platform-system risk

Information and decisions flow among all three tiers through:

  • Feedback
  • Communication
  • Continuous monitoring
  • Authorization reporting
  • Enterprise governance
  • Mission-area oversight

Risk Management Framework

The six RMF steps are:

  1. Categorize the system.
  2. Select security controls.
  3. Implement security controls.
  4. Assess security controls.
  5. Authorize the system.
  6. Monitor security controls.

The framework integrates cybersecurity into the complete system lifecycle.

Cybersecurity Reciprocity

Reciprocity permits DoD organizations to reuse credible authorization and assessment evidence produced by other organizations.

Effective reciprocity requires:

  • Transparent security documentation
  • Access to authorization packages
  • Common risk factors
  • Comparable control assessments
  • Traceable risk decisions
  • Information sharing among AOs and system owners
  • Continuing awareness of changes affecting authorization

Operational Resilience

Operational resilience requires:

  • Trustworthy information resources
  • Mission preparation for system degradation or loss
  • Effective network operations
  • Continuity under adverse cyber conditions
  • Dynamic allocation of remaining resources
  • Rapid restoration to a trusted state
  • Realistic exercises
  • Alternative operating procedures
  • Recovery while sustaining priority missions

The operational objective is for DoD missions to continue under adverse cyber conditions.

Cyberspace Defense

Cyberspace defense includes:

  • Detecting threats
  • Characterizing threats
  • Countering threats
  • Mitigating threats
  • Hardening systems
  • Restoring systems
  • Conducting defensive cyberspace operations
  • Coordinating enterprise defensive actions
  • Protecting DoD information
  • Protecting the DODIN
  • Recovering from incidents

Components may generally defend networks they own or operate within their assigned responsibility. Actions affecting more than one Component or areas outside the network owner’s authority require coordination through U.S. Cyber Command and Joint Force Headquarters–DODIN.

Continuous Monitoring

The Department maintains a continuous-monitoring capability supporting:

  • Collection of operational-security data
  • Transmission of monitoring data
  • Storage of monitoring data
  • Aggregation of security information
  • Presentation of current status
  • Enterprise situational awareness
  • Risk analysis
  • Vulnerability remediation
  • Authorization maintenance
  • Incident response

Components use a common:

  • Framework
  • Lexicon
  • Workflow
  • Reporting structure
  • Set of security-status concepts

Information Protection

Electronic DoD information must receive confidentiality, integrity, and availability protections appropriate to its importance and sensitivity.

Protected categories include:

  • Classified information
  • Sensitive compartmented information
  • Controlled unclassified information
  • Personally identifiable information
  • Privacy Act information
  • Protected health information
  • Proprietary information
  • Law-enforcement information
  • Export-controlled information
  • Mission-sensitive information

Systems processing CUI must be categorized at no less than a moderate confidentiality-impact level.

Information Markings and Metadata

Information should include standardized markings and metadata supporting:

  • Automated access decisions
  • Dissemination controls
  • Classification handling
  • CUI handling
  • Release restrictions
  • Auditability
  • Downstream protection
  • Secure information sharing

Public Release

Information proposed for publication through websites, blogs, social media, or other public Internet capabilities must undergo appropriate:

  • Public-release review
  • Security review
  • Classification review
  • CUI review
  • Operations-security review
  • Privacy review

System authorization does not constitute public-release approval.

Identity Assurance

The identity-assurance framework supports:

  • Strong identification
  • Strong authentication
  • Elimination of anonymous system use
  • User traceability
  • Non-person-entity traceability
  • Credential lifecycle management
  • Identity-attribute protection
  • Digital signatures
  • Encryption
  • PKI-based authentication
  • Biometrics

Public-Key Infrastructure

DoD-wide PKI supports:

  • Authentication
  • Digital signatures
  • Encryption
  • Certificate-based trust
  • Identity binding
  • Secure information sharing

Coalition PKI supports approved foreign mission partners communicating with Combatant Commands.

Identity Attributes

Access decisions may use attributes including:

  • Identity
  • Security clearance
  • Need to know
  • Organization
  • Role
  • Citizenship
  • Nationality
  • Mission assignment
  • Release authorization
  • Contractual relationship

A clearance alone does not establish unrestricted access to classified information.

DoD Information Technology Categories

DoD IT includes:

  1. Information systems
  2. Platform information technology
  3. IT services
  4. IT products

Information Systems

Information systems are commonly organized as:

  • Enclaves
  • Major applications

Enclaves

Enclaves provide shared capabilities such as:

  • Boundary defense
  • Incident detection
  • Incident response
  • Key management
  • Email
  • Office automation
  • Networks
  • Data-processing services
  • Common security controls

An enclave assumes the highest security category of the systems it hosts.

Major Applications

A major application requires special management oversight because loss, misuse, unauthorized access, or modification could cause significant harm.

It may consist of:

  • One application
  • Several related applications
  • Combined hardware and software
  • A mission-support capability
  • A business capability spanning several environments

Stand-Alone Systems

Stand-alone systems require authorization even when they are not connected to a network.

Security controls may be tailored based on:

  • Documented boundaries
  • Lack of connectivity
  • Actual system risks
  • AO approval

Platform Information Technology

Platform IT includes hardware and software that are:

  • Physically part of a special-purpose system
  • Dedicated to a special-purpose system
  • Essential in real time to a platform mission

Examples include:

  • Weapons systems
  • Vehicles
  • Aircraft
  • Ships
  • Medical devices
  • Building-control systems
  • Industrial-control systems
  • Utility systems
  • Fire-control systems
  • Facility automation

Platform IT Systems

A collection of platform IT may be designated as a PIT system when it has:

  • An identifiable boundary
  • Common security policy
  • Common authority
  • Defined system ownership
  • A formal authorization approach

PIT systems require assessors and authorizing officials familiar with their specialized mission, safety, timing, and reliability constraints.

IT Services

An IT service is a capability provided under a formal agreement by an internal or external provider.

Internal Services

Internal DoD service providers must:

  • Implement security controls
  • Assess supporting systems
  • Obtain authorization
  • Establish service-level agreements
  • Define provider and customer responsibilities
  • Report significant security changes

External Services

External service agreements and solicitations must address:

  • Cybersecurity requirements
  • Security controls
  • Assessment evidence
  • Incident reporting
  • Monitoring
  • Information protection
  • Operational reporting
  • Changes affecting security posture
  • Provider and customer responsibilities

Enterprise service agreements should be used when practical.

IT Products

IT products must satisfy applicable requirements involving:

  • Secure configuration
  • STIG compliance
  • SRG compliance
  • Interoperability
  • Connection approval
  • Security evaluation
  • Unified-capabilities certification
  • Trusted-systems-and-networks practices
  • Classified-information protection
  • Cryptographic approval

Products below the system level must be reviewed before being connected to an authorized environment.

Acquisition and Systems Engineering

Cybersecurity must be integrated into:

  • Requirements development
  • Acquisition planning
  • Systems engineering
  • Architecture
  • Contracting
  • Development
  • Testing
  • Evaluation
  • Fielding
  • Sustainment
  • Modification
  • Replacement
  • Disposal

Cybersecurity Strategy

Qualifying programs should maintain a cybersecurity strategy describing:

  • Requirements
  • Engineering
  • Architecture
  • Testing
  • Resources
  • Risk management
  • Supply-chain protection
  • Resilience
  • Authorization
  • Sustainment

The strategy should be reviewed before major milestone decisions and contract awards.

Systems Security Engineering

Systems-security engineering:

  • Identifies protection needs
  • Integrates controls into design
  • Supports risk analysis
  • Supports testing
  • Supports architecture
  • Addresses vulnerabilities
  • Supports trusted systems and networks
  • Maintains security throughout the lifecycle

Developmental Testing

Developmental testing examines:

  • Design implementation
  • Security-control maturity
  • Integration
  • Reliability
  • Resilience
  • Technical vulnerabilities
  • Interoperability

Operational Testing

Operational evaluation may include:

  • Independent penetration testing
  • Exploitation testing
  • Adversarial testing
  • Complete-system testing
  • Testing of cybersecurity service-provider controls
  • Mission-effectiveness assessment
  • Threat-representative conditions

Supply-Chain Risk and Trusted Systems

Trusted-systems-and-networks practices address:

  • Malicious insertion
  • Counterfeit components
  • Compromised suppliers
  • Global sourcing
  • Critical functions
  • Critical components
  • Replacement technology
  • Foreign collection
  • Battlefield loss
  • Design vulnerabilities

Criticality Analysis

Criticality analysis identifies components and functions whose compromise would cause the greatest mission harm.

It informs:

  • Supply-chain review
  • Engineering protections
  • Testing priorities
  • Procurement decisions
  • Program-protection planning
  • Sustainment decisions
  • Replacement-technology review

Security Controls and Configuration

Security Requirements Guides

SRGs organize security requirements for:

  • Technology categories
  • General product classes
  • Operating environments
  • Enterprise capabilities

Security Technical Implementation Guides

STIGs provide detailed configuration guidance for:

  • Specific products
  • Product versions
  • Operating systems
  • Databases
  • Network devices
  • Applications
  • Security tools

Exceptions must be documented and approved by the responsible AO.

Control Correlation Identifiers

A CCI expresses a security-control requirement as a single actionable and measurable statement.

CCIs support:

  • Automated testing
  • Compliance tracking
  • Control implementation
  • Assessment
  • Reporting
  • Mapping among standards

Security Content Automation Protocol

SCAP supports machine-readable:

  • Configuration requirements
  • Vulnerability checks
  • Assessment definitions
  • Compliance results
  • Security automation

Cybersecurity Knowledge Repositories

Knowledge repositories provide community memory through:

  • Standards
  • Benchmarks
  • Templates
  • Checklists
  • Tools
  • Rules
  • Best practices
  • Assessment content
  • Vulnerability information
  • Implementation guidance

Examples include:

  • DoD Cyber Exchange
  • RMF Knowledge Service
  • National Vulnerability Database
  • Open Vulnerability and Assessment Language Repository

Organizational Responsibilities

DoD Chief Information Officer

The DoD CIO:

  • Establishes cybersecurity policy
  • Advises the Secretary of Defense
  • Oversees program implementation
  • Appoints key cybersecurity officials
  • Coordinates with intelligence leadership
  • Coordinates with other security disciplines
  • Oversees enterprise cybersecurity resources
  • Establishes continuous-monitoring policy
  • Establishes cross-domain policy
  • Conducts annual Component assessments
  • Supports cybersecurity metrics and scorecards
  • Chairs or appoints leadership for supporting governance bodies

DoD Senior Information Security Officer

The DoD SISO:

  • Directs and coordinates the DoD cybersecurity program
  • Develops policy and control procedures
  • Supports the DoD CIO
  • Coordinates enterprise metrics
  • Oversees cybersecurity budgeting
  • Coordinates with authorizing officials
  • Coordinates with system owners
  • Coordinates with NIST and the intelligence community
  • Supports acquisition reviews
  • Advocates enterprise cybersecurity solutions

Defense Information Systems Agency

DISA:

  • Develops and manages cybersecurity for DISN
  • Supports DODIN operations
  • Develops CCIs
  • Develops SRGs and STIGs
  • Maintains the DoD Cyber Exchange
  • Supports connection approval
  • Supports ports, protocols, and services governance
  • Supports cross-domain connections
  • Conducts cyber-readiness inspections
  • Supports cybersecurity repositories
  • Provides enterprise cybersecurity solutions
  • Supports multinational cybersecurity cooperation

Commander, U.S. Cyber Command

Commander, USCYBERCOM:

  • Directs DODIN operations and defense
  • Issues cybersecurity orders and directives
  • Coordinates enterprise defensive actions
  • Chairs the DoD risk-management committee
  • Directs command cyber-readiness inspections
  • Coordinates actions affecting multiple Components
  • Supports continuous monitoring
  • Integrates cybersecurity with cyberspace defense

National Security Agency

NSA:

  • Provides cybersecurity architecture expertise
  • Develops cryptographic solutions
  • Approves algorithms protecting classified information
  • Supports PKI
  • Supports systems-security engineering
  • Evaluates cybersecurity products
  • Supports threat and vulnerability assessment
  • Develops technical specifications
  • Supports SRG and STIG development
  • Manages cryptographic key infrastructure

Defense Intelligence Agency

DIA:

  • Provides cyber-threat intelligence
  • Provides threat assessments
  • Manages cybersecurity for non-cryptographic SCI systems
  • Supports the DoD intelligence environment
  • Supports JWICS cybersecurity

Defense Counterintelligence and Security Agency

DCSA:

  • Oversees cleared-contractor information-system security
  • Monitors contractor cybersecurity practices
  • Enforces industrial-security requirements
  • Supports authorization and inspection
  • Oversees vendors processing classified DoD information

DoD Component Heads

Component heads:

  • Establish Component cybersecurity programs
  • Assign all DoD IT to accountable cybersecurity programs
  • Appoint authorizing officials
  • Identify and register PIT systems
  • Provide incident-response capabilities
  • Provide vulnerability-management capabilities
  • Maintain cybersecurity monitoring
  • Ensure contract requirements
  • Ensure workforce qualification
  • Provide user training
  • Protect privacy
  • Support accessibility
  • Conduct assessments
  • Report system data
  • Enforce configuration requirements
  • Implement U.S. Cyber Command direction

Component Chief Information Officers

Component CIOs:

  • Establish and enforce Component cybersecurity programs
  • Appoint Component SISOs
  • Coordinate with acquisition executives
  • Ensure early management of cybersecurity acquisition risk
  • Resolve major-application classification disputes
  • Control code-signing-certificate designations
  • Maintain alignment with DoD cybersecurity strategy

Cybersecurity Workforce

The cybersecurity workforce must be:

  • Identified
  • Assigned in writing
  • Properly designated
  • Trained
  • Qualified
  • Suitable
  • Fit for duty
  • Continuously developed

Workforce Positions

Examples include:

  • Component SISO
  • AO
  • System owner
  • Information owner
  • ISSM
  • ISSO
  • Security-control assessor
  • System administrator
  • Network administrator
  • Cybersecurity service-provider personnel
  • PKI personnel

Non-U.S. Citizens

Under specified conditions, non-U.S. citizens may:

  • Serve as system administrators
  • Maintain cybersecurity-enabled products
  • Perform approved technical functions

They must:

  • Meet investigative requirements
  • Work under immediate U.S.-citizen supervision
  • Remain within authorized duties

They may not serve in certain positions, including:

  • ISSM
  • ISSO
  • Supervisory cybersecurity positions
  • PKI certificate-issuance authority

Incident Response

Components must provide capabilities to:

  • Mitigate vulnerabilities
  • Respond to cyber incidents
  • Limit damage
  • Restore services
  • Support cyberspace defense
  • Collect audit data
  • Preserve investigative evidence
  • Report classified compromise
  • Report CUI disclosure
  • Report contractor incidents
  • Report privacy breaches
  • Comply with U.S. Cyber Command orders

Information Spillage

Information spillage includes:

  • Classified information placed on an unclassified system
  • Higher-classification information placed on a lower-classification system
  • Information placed on a system not authorized to process it

Response may require:

  • Containment
  • Reporting
  • Investigation
  • Sanitization
  • Credential changes
  • System reconstruction
  • Impact assessment
  • Coordination with security and law-enforcement authorities

Cybersecurity Testing

Cybersecurity testing may include:

  • Security-control assessment
  • Vulnerability assessment
  • Penetration testing
  • Exploitation testing
  • Red Team assessment
  • Blue Team assessment
  • Cyber-readiness inspection
  • Developmental testing
  • Operational testing
  • Interoperability testing
  • Exercise-based resilience testing

Testing should examine:

  • Systems
  • Enclaves
  • Applications
  • Platform systems
  • Service providers
  • Common controls
  • Mission dependencies
  • Recovery procedures

Communications and Cryptography

Communications Security

COMSEC protects information through:

  • Approved cryptographic equipment
  • Keying material
  • Procedures
  • Monitoring
  • Controlled handling

Transmission Security

TRANSEC protects communications against exploitation of transmission characteristics.

TEMPEST

TEMPEST requirements address compromising emanations from electronic equipment.

Components must fund and implement required countermeasures under applicable national guidance.

Mission Partners

Cybersecurity cooperation with mission partners supports:

  • Interoperability
  • Information sharing
  • Collective defense
  • Critical-infrastructure protection
  • Training
  • Exercises
  • Capacity building
  • Global cyber situational awareness

Formal Agreements

Mission-partner capabilities require formal agreements addressing:

  • Risk
  • Security responsibilities
  • Information protection
  • Operations
  • Sustainment
  • Disclosure
  • Access
  • Incident response
  • Service levels
  • Legal authority

Foreign Access

Foreign personnel may access DoD systems containing classified or sensitive information only when:

  • A Component head authorizes access
  • Disclosure guidance permits access
  • Technical controls restrict information appropriately
  • Information has been cleared for release
  • Identity and access requirements are satisfied

DoD-Partnered Systems

A DoD-partnered system is jointly developed or operated with non-DoD mission partners.

Examples may include:

  • Coalition systems
  • Multinational systems
  • Interagency systems
  • First-responder systems
  • Shared mission environments

User Responsibilities

Privileged Users

Privileged users must:

  • Operate only within authorized privileges
  • Follow approved configuration requirements
  • Protect administrative credentials
  • Report security changes
  • Report vulnerabilities
  • Avoid unauthorized configuration changes
  • Maintain accountability for privileged actions

Authorized Users

Authorized users must:

  • Protect passwords, tokens, certificates, and other authenticators
  • Protect assigned devices
  • Complete awareness training
  • Report incidents and suspicious activity
  • Report loss of access requirements
  • Use only approved hardware and software
  • Avoid bypassing security controls
  • Obtain authorization before relocating equipment
  • Use systems only for official or otherwise authorized purposes
  • Follow cybersecurity and operations-security policy
Downloads last month
120
Total file size:
1.04 MB