You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Non-Fungible Token Security say about Transferable (Section 3.3.1.2)? According to Non-Fungible Token Security, Transferable (Section 3.3.1.2): 5. There is likely no smart contract mechanism to restore stolen tokens to their rightful owner. 6. If a smart contract enables the contract manager to restore stolen tokens, this feature could be used by the manager to confiscate, freeze, or unilaterally transfer tokens. 7. A smart contract may not allow a manager to restore stolen tokens, but the smart contract may have a manager-controlled update mechanism whereby this feature could be added in the future (enabling the previously mentioned security concern). 8. Coding errors in the smart contract could enable attackers to steal tokens and transfer them to their accounts.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Non-Fungible Token Security.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about 5.5 Claim of Supported Test Assertions? (Part 2) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, 5.5 Claim of Supported Test Assertions: No) there are any known deviations from (or exceptions to) the requirements found in the base standard and identified in the Conformance Testing Methodology for the associated Record Types in the IUT. For specific exceptions, the Implementation Support column of the tables of requirements and assertions can be used to indicate the difference on a per-assertion basis. In addition, if the deviation is general and applies to the entire Record Type, a description should be provided. This option is useful for cases where there have been modifications to the base standard that are not reflected in the conformance testing methodology, where the IUT provider believes there is a defect in the base standard or conformance testing methodology, and other instances where the implementation does not fully conform to the AN-2013 standard requirements. The testing laboratory may use testing tools that implement this CTMF and any the test assertions included in any derivative conformant publications (such as those which document additional requirements) to provide a determination of the level of conformance of the IUT to the AN-2013 standard.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-220 in Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)? (Part 177) Control PA-220: Administrator OM-NET-001 Network Operations Specialist | | Specific product used | How the component functions in the build | Applicable Cybersecurity Framework Version 1.1 Subcategories | Applicable NIST SP 800-53 Revision 4 Controls | ISO/IEC 27001:2013 | CIS 6 | NIST SP 800-181 NICE Framework Work Roles | |-------------------------|--------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| | | | | | Transfer Policies and Procedures A.14.1.2 Securing Application Services on Public Networks A.14.1.3 Protecting Application Services Transactions | CSC 15 Wireless Access Control CSC 18 Application Software Security | | | | | PR.AC-6- Identities are proofed and bound to credentials and asserted in interactions | Access Control AC- 1, AC-2, AC-3, AC- 16, AC-19, AC-24 Identification and Authentication IA- 1, IA-2, IA-4, IA-5, IA-8 Physical and Environmental Protection PE-2, PS-3 | A.7.1.1 Screening A.9.2.1 User Registration and De-Registration | CSC 16 Account Monitoring and Control | OV-SPP-002 Cyber Policy and Strategy Planner OV-MGT-002 Communications Security (COMSEC) Manager OM-ADM-001 System Administrator | | Specific product used | How the component functions in the build | Applicable Cybersecurity Framework Version 1.1 Subcategories | Applicable NIST SP 800-53 Revision 4 Controls | ISO/IEC 27001:2013 | CIS 6 | NIST SP 800-181 NICE Framework Work Roles | |-------------------------|--------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |

Explanation: NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Developing Trust Frameworks to Support Identity Federations say about Identity Management Programs and Other Resources? According to Developing Trust Frameworks to Support Identity Federations, Identity Management Programs and Other Resources: - The Vocabulary of Identity System Liability , The Open Identity Exchange/Edwards Wildman Palmer LLP, by Thomas J. Smedinghoff, Mark Deem, and Sam Eckland. - TeleSign Consumer Account Security Report, An International Study of Digital Security Concerns and Practices.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Trust Frameworks to Support Identity Federations.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 105) • directory service and console access manager components on the OT network (i.e., ensuring that only authorized users can access and add, modify, or delete information on these components) • IT network access-control switch that serves as a gateway to the OT network from the IT network ▪ protecting the integrity of the information exchanges between the following components: • • identity manager and the identity stores identity store and the directory service on the OT network • directory service and the console access manager components on the OT network, as well as the network access-control and policy-enforcement system within the IT network • network access-control and component identity stores • network access-control component on the IT network and the IT network access-control switch that serves as a gateway to the OT network Based on the information flows for supporting PACS authentication, PACS access control, and PACS authorization described in Section 5.6.7, securing the part of the IdAM example solution that supports PACS access control requires the following actions: ▪ securing access to the following components: • • identity, authorization, and workflow manager; identity store; and IdAM translator components on the IdAM network (i.e., ensuring that only authorized users can

Explanation: NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Identity and Access Management for Electric Utilities.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile say about 7. Manufacturing Profile Subcategory Guidance? (Part 110) According to Cybersecurity Framework Manufacturing Profile, 7. Manufacturing Profile Subcategory Guidance: Low, Moderate and High Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly. | 62443-2-1:2009 4.3.4.5.10 IR-4 | | | Improvements (RS.IM) | | Low, Moderate and High Update the response plans to address changes to the organization, manufacturing system, attack vectors, or environment of operation and problems encountered during plan implementation, execution, or testing. Updates may include, for example, responses to disruptions or failures, and predetermined procedures. Enable a process for the response plan to evolve to reflect new threats, improved technology, and lessons learned.

Explanation: NIST cybersecurity publication covering vulnerability management. Topics: attack vector, incident response. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Framework Manufacturing Profile.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-5 in A Threat Analysis on UOCAVA Voting Systems? (Part 45) Control IA-5: tered voter (e.g, forged signature). | Hostile Individuals Hostile Individuals | Mod. Mod. | Mod. Mod. | Integrity-Mod. Integrity-Mod. | IA-1, IA-2, IA-4, IA-5, IA-7 IA-1, IA-2, IA-4, IA-5, IA-7 | | Voter coerced into voting a particular way. Voter coerced into voting a particular way. | Hostile Individuals Hostile Organizations Hostile Individuals Hostile Organizations | Low Low | Mod Mod | Confid.-Mod Confid.-Mod | Outside control of officials. Outside control of officials. | | Election official offices have too few fax machines and/or telephone lines to handle demand. Election official offices have too few fax machines and/or telephone lines to handle demand. | Telephone Operators System Operators Telephone Operators System Operators | Low Low | High High | Avail.-High Avail.-High | IR-4, IR-5 IR-4, IR-5 | | A denial of service attack against the election official office jams fax machines and/or telephone lines. A denial of service attack against the election official office jams fax machines and/or telephone lines. | Telephone Operators Hostile Organizations Telephone Operators Hostile Organizations | Mod. Mod. | High High | Avail.-High Avail.-High | IR-4, IR-5, CP-7, CP-8, SC-5 IR-4, IR-5, CP-7, CP-8, SC-5 | | Personally identifiable material is intercepted en route. Personally identifiable material is intercepted en route. | Telephone Operators Hostile Organizations Telephone Operators Hostile Organizations | High High | Low Low | Confid.-Mod. Confid.-Mod.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-5 in A Threat Analysis on UOCAVA Voting Systems? (Part 79) Control IA-5: | X | INCIDENT HANDLING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | IR-5 | X | X | INCIDENT MONITORING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | MA-2 | | X | CONTROLLED MAINTENANCE | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-3 | | X | MAINTENANCE TOOLS | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-5 | | X | MAINTENANCE PERSONNEL | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | PE-2 | X | X | PHYSICAL ACCESS AUTHORIZATIONS | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment. | | PE-3 | X | X | PHYSICAL ACCESS CONTROL | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment.

Explanation: NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Threat Analysis on UOCAVA Voting Systems.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2019 NIST_ITL Cybersecurity Program Annual Report provide? (Section 22) Framework. Since NIST has researched industry practices in cyber supply chain risk management (C-SCRM) through engagement with industry leaders, the group was able to identify some helpful practices. The NISTIR is based on an analysis of interviews with companies over several years (leading to the development of 24 case studies), prior NIST research in cyber supply chain risk management, and several standards and industry best practices documents. CREDIT: Shutterstock / faithie <!-- image --> Network and data security are essential in today's environment of increasingly open and interconnected systems, networks, and mobile devices. Cryptographic standards, algorithms, and methods for encryption, key establishment, and digital signatures provide a critical foundation for mobile device conversations, secure e-Commerce transactions, electronic lock access, and much more. Cryptography is a continually evolving field that drives research and innovation. The Data Encryption Standard (DES) was groundbreaking but today would fall far short of the necessary levels of protection. The accomplishments below demonstrate NIST's continued dedication to the role it has fulfilled for nearly 50 years-leading public and private collaborations to foster continued improvement and reliability in cryptographic techniques and technology. In recent years, there has been a substantial amount of research on quantum computers-machines that exploit quantum mechanical phenomena to solve mathematical problems that are difficult or intractable for conventional computers. When the capacity to build large-scale quantum computers exists, they will be able to break many of the public-key cryptosystems currently in use. This would seriously compromise the confidentiality and integrity of digital communications on the internet and elsewhere.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2019 NIST_ITL Cybersecurity Program Annual Report.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Section 14) istry [4]. The requirements do not apply to nonfederal organizations that are collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency. 8 The security requirements in this publication are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. 9 The requirements are intended for use by federal agencies in contractual vehicles or other agreements that are established between those agencies and nonfederal organizations. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for nonfederal organizations. If nonfederal organizations designate system components for the processing, storage, or transmission of CUI, those organizations may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by applying architectural and design concepts (e.g., implementing subnetworks with firewalls or other boundary protection devices and using information flow control mechanisms). Security domains may employ physical separation, logical separation, or a combination of both. This approach can provide adequate security for CUI and avoid increasing the organization's security posture beyond what it requires for protecting its missions, operations, and assets. The remainder of this special publication is organized as follows: - Section 2 describes the assumptions and methodology used to develop the security requirements for protecting the confidentiality of CUI, the format of the requirements, and the tailoring criteria applied to the NIST guidelines to obtain the requirements. - Section 3 lists the security requirements for protecting the confidentiality of CUI in nonfederal systems and organizations.

Explanation: NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity? (Part 111) Control AC-1: admin user. 4. Setup and configure network settings for FTD. Ensure that the device will not be managed locally and that the FTD system will run in transparent mode. <!-- image --> <!-- image --> 5. Configure the manager settings with the IP address of ISE and a registration key. The key opted to use in this build is cisco123 . This key is required for integration into FMC. ## 2.3.3.2 Cisco Firepower Management Center Installation and Configuration 1. Obtain OVF and VMDK file from Cisco representative and deploy to virtual environment. Power on VM after deployment is completed. 2. Open VM Console and log in with username admin and password Admin123 . Once logged in, view and accept the EULA. 3. Configure network for FMC system. DHCP was utilized in this setup. Type y to verify configuration. 4. Once logging in to the web interface for FMC, click the gear icon in the top left, then select Integration. Select the tab at the top entitled Identity Sources . 5. Fill out each line for the ISE instance. IP address or Fully Qualified Domain Name (FQDN), the pxGrid Server certificate authority is the self-signed certificate in ISE, the same certificate is used for the MNT certificate, and the FMC Server Certificate is the certificate generated in ISE for the pxGrid. Ensure that the checkboxes for Session Directory Topic and SXP Topic are selected. Click Test to verify successful connection, then click Save . <!-- image --> <!-- image --> <!-- image --> 6. To add the FTD, select Device > Device Management , then click Add. 7. On the pop-up window, fill in all blanks, with the Host as the IP address of the FTD, a Display Name , and place copy the registration key created earlier to Registration Key . The lab used cisco123 as the registration key. For Access Control Policy , click the drop-down box, then select Create New Policy . Give it a name, description, and ensure Block all traffic is selected as the default action. Click Save . <!-- image --> <!-- image --> 8.

Explanation: NIST publication on credential and access management. Topics: access control, certificate authority. Contains security framework guidance for authentication systems. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute Considerations for Access Control Systems say about Executive Summary? (Part 3) According to Attribute Considerations for Access Control Systems, Executive Summary: annot be accessed during an information system emergency (e.g., low bandwidth, loss of service). In addition, the fail over and backup capability of attribute repositories need to be considered. Management provides mechanisms for maintaining attributes to ensure the efficiency and consistent use of attributes, including metadata, hierarchical structures for attribute grouping, minimization and transformation methods for attribute performance, and additional support capabilities (e.g., attribute integration with authentication, logs for recording attribute access and updates). NIST Special Publication (SP) 800-162, Guide to Attribute Based Access Control (ABAC) Definition and Considerations [1], introduced guidance on access control definitions and considerations for the implementation of access control systems but did not include detailed recommendations on considerations such as the preparation, veracity, security, readiness, and management of attributes. This document aims to provide federal agencies with a guide to attribute considerations with Attribute Evaluation Scheme examples for access control. The Attribute Evaluation Scheme should be determined by an enterprise information system's requirements, and the enterprise information system should validate these requirements to realize the appropriate organizational attribute evaluation scheme capability in line with performance and cost recommendations. Note that this document does not establish a universal attribute scheme that suits all business capabilities and performance requirements; instead, it provides considerations and examples that can be adapted to meet the specific needs of an organization when defining its attribute evaluation scheme. 6

Explanation: NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Attribute Considerations for Access Control Systems.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 03.01.05 Least Privilege according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 03.01.05 Least Privilege: - a. Allow only authorized system access for users (or processes acting on behalf of users) that is necessary to accomplish assigned organizational tasks. - b. Authorize access to [ Assignment: organization-defined security functions ] and [ Assignment: organization-defined security-relevant information ]. - c. Review the privileges assigned to roles or classes of users [ Assignment: organization-defined frequency ] to validate the need for such privileges. - d. Reassign or remove privileges, as necessary.

Explanation: NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Training & Awareness Course Compendium provide? (Section 93) such that as problems arise, the student will be able to recognize, in a working environment, that legal issues must be addressed. COURSE TITLE: GBA 577: Advanced EDP Auditing COURSE LENGTH: 3.5 HRS. California State Polytechnic Univ, Pomona College of Business Administration Computer Information Systems Department 3801 West Temple Avenue Pomona, CA 91768-4083 Dan Manson: (714) 869-3244 Auditing in a computer information systems environment involves evidence that originates or is maintained in a computer system. The course provides students with an understanding of the role of the EDP Audit function, the purpose of controls in a computer environment, and skills required to perform EDP Audits. Advanced concepts in EDP Auditing. Understanding EDP controls, types of EDP audits, risk assessment and concepts, and techniques used in EDP audits. Prerequisite: CIS 433 or permission of instructor. COURSE TITLE: Computer Security for the End-User COURSE LENGTH: 1 DAY VENDOR: COMSIS 8737 Colesville Road, Suite 1100 Silver Spring, MD 20910 Ronald E. Freedman: (301) 588-0800 This course provides training to end-users who operate sensitive and mission-critical systems and/or rely upon automated information systems to perform their work. COURSE TITLE: Information Systems Security (CSI 214) COURSE LENGTH: 1 SEMESTER Anne Arundel Community College Engineering and Computer Technology Careers 219 101 College Parkway Arnold, MD 21012-1895 Gail Reese: (410) 541-2758 A survey of topics in data retention and control and techniques associated with data, computer systems, network and installation security. The student will obtain skills related to occupations in data libraries and data security at computer installations. NOTE: Three semester hours; prerequisite: CSI 113 or permission of department head. COURSE TITLE: COURSE LENGTH: 2 DAYS TEMPEST Program Management and Systems Engineering Security Engineering Services, Inc.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does CVSS Implementation Guidance provide? (Section 32) 4 Affecting the application. This section showcases a list of example vulnerabilities scored via the CVSS to assist vulnerability analysts in scoring vulnerabilities via the CVSS. The scores are based on information provided by the NVD and includes the CVE ID, CWE ID, CVSS base score, CVSS vector, a description of the vulnerability, and a justification for each CVSS base score. Mozilla Firefox before 17.0, Firefox ESR 10.x before 10.0.11, Thunderbird before 17.0, Thunderbird ESR 10.x before 10.0.11, and SeaMonkey before 2.14 implement cross-origin wrappers with a filtering behavior that does not properly restrict write actions, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted web site. The scoring template for Cross-site Scripting takes into consideration SCORING TIP #2 which states: 'When scoring a vulnerability, consider the direct impact to the target host only. For example, consider a cross-site scripting vulnerability: the impact to a user's system could be much greater than the impact to the target host. However, this is an indirect impact.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) say about threat? According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), threat: Any circumstance or event with the potential to adversely impact organizational operations, organizational assets, individuals, other organizations, or the Nation through a system via unauthorized access, destruction, disclosure, modification of information, or denial of service. [NIST-SP-800-53]

Explanation: NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about 11.4.1 Errors Encountered During Normal Operation? According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, 11.4.1 Errors Encountered During Normal Operation: Many errors that occur during normal operation may be caused by a consuming application's improper DRBG request or possibly the current unavailability of entropy; these errors are indicated by 'ERROR\_FLAG ' in the pseudocode. In these cases, the consuming application user is responsible for correcting the request within the limits of the user's organizational security policy. For example, if a failure indicating an invalid requested security strength is returned, a security strength higher than the DRBG or the DRBG instantiation can support has been requested. The user may reduce the requested security strength if the organization's security policy allows the information to be protected using a lower security strength, or the user shall use an appropriately instantiated DRBG. Catastrophic errors (i.e., errors indicated by the CATASTROPHIC\_ERROR\_FLAG in the pseudocode) detected during normal operation shall be treated in the same manner as an error detected during health testing (see Section 11.4.2).

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 206) Control IP-002: art grid marketplace. Implementation of the IPRM will lead to reduced deployment costs of smart grid systems and devices, and enhanced product quality with respect to interoperability and conformance. This will ultimately provide increased end-user customer satisfaction and confidence to the buyer through meaningful certification programs. For instance, as electric utilities turn to Advanced Metering Infrastructures (AMIs) to promote the development and deployment of the smart grid, one aspect that can benefit from 34 The Companion Spreadsheet to the Guide for Assessing the High-Level Security Requirements in NISTIR 7628 is available at: 35 IPRM Version 2.0, January 2012. sggrid/pub/SmartGrid/SmartGridTestingAndCertificationCommittee/IPRM_final_-_011612.pdf 215 standardization is the upgradeability of Smart Meters. The National Electrical Manufacturers Association (NEMA) standard SG-AMI 1-2009, Requirements for Smart Meter Upgradeability, describes functional and security requirements for the secure upgrade—both local and remote— of smart meters. Draft NISTIR 7823, Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, describes conformance test requirements that may be used voluntarily by testers and/or test laboratories to determine whether smart meters and upgrade management systems conform to the requirements of NEMA SG-AMI 1-2009. 216 CHAPTER 4 CRYPTOGRAPHY AND KEY MANAGEMENT This chapter identifies technical cryptographic and key management issues across the scope of systems and devices found in the smart grid along with potential alternatives. The identified alternatives may be existing standards, methods, or technologies, and their optimal adaptations for the smart grid.

Explanation: NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Procedure Examine the VC attached to the RUT to verify that it is not storing any ROAs that cover the following three addresses:? (Part 3) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Procedure Examine the VC attached to the RUT to verify that it is not storing any ROAs that cover the following three addresses:: t the second and third ROAs are no longer in the repository): - (10.10.128.128/19, 19, AS 65501) is present. - (10.10.128.192/19, 19, AS 65501) is absent. - (10.10.128.224/19, 19, AS 65501) is absent. - Wait for an amount of time to elapse that is greater than the RPKI -to-VC content update interval, or, alternatively, force the validator/VC to be updated with the latest RPKI repository information. - Verify that a VRP for only the first ROA created in Step 4 above has been received by the VC that is attached to the RUT. - Wait for an amount of time to elapse that is greater than the VC-to-router refresh interval. - Verify that a VRP for only the first ROA created in Step 4 is received by the RUT (i.e., no VRP for the second or third ROA is received by the router). (Use the show ip bgp rpki table command at the RUT to list the VRP information that it has received from its VC.)

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Testing of Equipment according to Accuracy, Integrity, and Security in Computerized Vote-Tallying? Testing of Equipment: Each unit of tabulating equipment shall be tested "using all applicable ballot formats."

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 171) | A major subdivision or component of an information system consisting of information, information technology, and personnel that performs one or more specific functions. | | Supplementation (Security Controls) | The process of adding security controls or control enhancements to a security control baseline from NIST Special Publication 800-53 or CNSS Instruction 1253 in order to adequately meet the organization's risk management needs. | | System | See Information System . | | System Security Plan [NIST SP 800-18] | Formal document that provides an overview of the security requirements for an information system and describes the security controls in place or planned for meeting those requirements. | | System-Specific Security Control [NIST SP 800-37] | A security control for an information system that has not been designated as a common control or the portion of a hybrid control that is to be implemented within an information system. | | Tailoring [NIST SP 800-53, CNSSI 4009] | The process by which a security control baseline is modified based on: (i) the application of scoping guidance; (ii) the specification of compensating security controls, if needed; and (iii) the specification of organization-defined parameters in the security controls via explicit assignment and selection statements. | | Tailored Security Control Baseline | A set of security controls resulting from the application of tailoring guidance to the security control baseline. See Tailoring .

Explanation: NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations provide? (Section 7) nd structured process that integrates information security and risk management activities into the system development life cycle. Ongoing monitoring is a critical part of that risk management process. In addition, an organization's overall security architecture and accompanying security program are monitored to ensure that organization- wide operations remain within an acceptable level of risk, despite any changes that occur. Timely, relevant, and accurate information is vital, particularly when resources are limited and agencies must prioritize their efforts. Information security continuous moni toring (ISCM) is defined as maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions. Any effort or process intended to support ongoing monitoring of information security across an organization begins with leadership defining a comprehensive ISCM strategy encompassing technology, processes, procedures, operating environments, and people. This strategy: - Is grounded in a clear understanding of organizational risk tolerance and helps officials set priorities and manage risk consistently throughout the organization; - Includes metrics that provide meaningful indications of security status at all organizational tiers; - Ensures continued effectiveness of all security controls; - Verifies compliance with information security requirements derived from organizational missions/business functions, federal legislation, directives, regulations, policies, and standards/guidelines; - Is informed by all organizational IT assets and helps to m aintain visibility into the security of the assets; - Ensures knowledge and control of changes to organizational systems and environments of operation; and - Maintains awareness of threats and vulnerabilities.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio say about Comparing ICTRM and ERM? (Part 2) According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio, Comparing ICTRM and ERM: zation. The enterprises discussed in this publication have more complex compositions [IR8170] . Most ICTRM responsibilities tend to be carried out by the individual organizations within an enterprise. In contrast, the ERM responsibility for tracking key enterprise risks and their impacts on objectives is at the highest-level enterprise, held by top-level corporate officers and board members who have fiduciary and reporting duties not performed elsewhere in the enterprise. ERM requires identifying and understanding the various types of risk, including ICT risks, that an enterprise faces; determining the probability that these risks will occur; and estimating their potential impact. ERM processes provide senior enterprise executives with a portfolio view of key risks across the enterprise, and this portfolio considers the outputs of all ICTRM disciplines. 6 Public and private enterprises have a common primary purpose for ERM: safeguard the enterprise's mission, finances (e.g., net revenue, capital, free cash flow), and reputation (e.g., stakeholder trust) in the face of natural, accidental, and adversarial threats.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results say about Other Security Concerns? According to Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results, Other Security Concerns: Non-repudiation ; The workshop was unable to reach agreement as to whether this concept should be additionally included as a separate security objective. Some participants in the workshop noted that the international standard on security architecture, ISO 7498-21988(E) , in its section 5.2, includes non-repudiation as a security service "which can be provided optionally within the framework of the OSI Reference Model." In the ISO standard, non-repudiation is defined (section 5.2.5) as providing "proof" to one of the parties to the interchange against a false denial of involvement by the other party. The ISO standard, however, contemplates that only cryptographic techniques can provide non-repudiation. Other workshop participants asserted that it is the role of a third-party arbiter, such as a judge, arbitrator or jury, to consider the evidentiary weight of any denial of involvement. In such a situation, the demonstrated comparative trustworthiness of documented audit trails will likely determine which party will prevail. Proposition 14 (see below) reflects this view, and suggests that VANs, under certain circumstances, could provide the necessary evidence for non-repudiation System-wide Security : While the propositions presented below primarily concern security of the EDI link between interchange partners, users of EDI must be concerned also with the security of their own and their interchange partner's internal systems. It must be recognized that the EDI process encompasses three broad phases -origination, transmission, and reception. Proposition 6 sets forth a necessary relationship between link security and system-wide security.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about SECURITY AND PRIVACY IN THE RMF? According to NIST_SP_800-37r2_Risk_Management_Framework, SECURITY AND PRIVACY IN THE RMF: Organizations are encouraged to collaborate on the plans, assessments, and plans of action and milestones (POAM) for security and privacy issues to maximize efficiency and reduce duplication of effort. The objective is to ensure that security and privacy requirements derived from laws, executive orders, directives, regulations, policies, standards, or missions and business functions are adequately addressed, and the appropriate controls are selected, implemented, assessed, and monitored on an ongoing basis. The authorization decision, a key step in the RMF, depends on the development of credible and actionable security and privacy evidence generated for the authorization package. Creating such evidence in a cost-effective and efficient manner is important. The unified and collaborative approach to bring security and privacy evidence together in a single authorization package will support authorizing officials with critical information from security and privacy professionals to help inform the authorization decision. In the end, it is not about generating additional paperwork, artifacts, or documentation. Rather, it is about ensuring greater visibility into the implementation of security and privacy controls which will promote more informed, risk-based authorization decisions. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Explanation: NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 215) 140-2, Security Requirements for Cryptographic Modules | http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf | | FIPS 186-2, Digital Signature Standard | change1.pdf | | FIPS 196, Entity Authentication Using Public Key Cryptography | http://csrc.nist.gov/publications/fips/fips196/fips196.pdf | | FIPS 201-1, Personal Integrity Verification of Federal Employees and Contractors | chng1.pdf | | HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors | 8.html | | IR 7298, Glossary of Key Information Security Terms | 7298_Glossary_Key_Infor_Security_Terms.pdf | | Standard | URL | |--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| | SP 800-21-1, Guideline for Implementing Cryptography in the Federal Government | 1_Dec2005.pdf | | SP 800-25, Federal Agency Use of Public Key Technology for Digital Signatures and Authentication | | | SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure | http://csrc.nist.gov/publications/nistpubs/800-32/sp800-32.pdf | | SP 800-44, Guidelines on Securing Public Web Servers | | | SP 800-57, Special Publication on Key Management | Part1.pdf | | SP 800-92, Guide to Computer Security Log Management | http://csrc.nist.gov/publications/nistpubs/800-92/SP800-92.pdf | | SP 800-100, Information Security Handbook: A Guide for Managers | Mar07-2007.pdf | | Organization | URL | |------------------------------------------------------------------------------|--------------------------------| | Standards Bodies | | | IEEE Computer Society Technical Committee on Services

Explanation: NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework say about Test Steps? According to Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, Test Steps: 1. Tester shall install Image A on a Test Smart Meter. 2. Tester shall configure the Smart Meter as documented in the Vendor's response to RVI.NEMA-7.1. 3. Tester shall document the configuration. 4. Tester shall follow the methods in the Vendor's response to RVI.NEMA-3.1 to install Image B on the Test Smart Meter. 5. Based on the Vendor's response to RVI.NEMA-7.2, Tester shall verify that the Smart Meter's configuration persisted by comparing to the configuration documented in test step 3.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 84) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: B | | RT1.29 - Fie ld: 1.004- TOT- CharCount | Table 22 | Table 22 specifies the character count for each field. | 1 | 1.004-TOT- CharCount | MO ( Count(Chars({Fld(1.004)}), Set-Int([1 to 16]) ) | | M-Fld(1.004) | | | | B | | RT1.30 - Fie ld: 1.005- DAT- FieldStructu | Table 22, Annex B, Annex G | Table 22 specifies which fields contain subfields and information items as well as the number of occurrences permitted. | 1 | 1.005-DAT- SubfieldCou nt | EQ ( Count(SubFldsIn(Fld(1.005))), Int(1) | | M-Fld(1.005) | | | | T | | re | | Afield contains a minimum of one subfield which contains a minimum of one information item.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ Methods and Techniques say about F.3.14 CFB128-AES128.Decrypt? According to Recommendation for Block Cipher Modes of Operation_ Methods and Techniques, F.3.14 CFB128-AES128.Decrypt: Key IV Segment #1 Input Block Output Block Ciphertext Plaintext Segment #2 Input Block Output Block Ciphertext Plaintext Segment #3 Input Block Output Block Ciphertext Plaintext Segment #4 Input Block Output Block Ciphertext Plaintext 2b7e151628aed2a6abf7158809cf4f3c 000102030405060708090a0b0c0d0e0f 000102030405060708090a0b0c0d0e0f 50fe67cc996d32b6da0937e99bafec60 3b3fd92eb72dad20333449f8e83cfb4a 6bc1bee22e409f96e93d7e117393172a 3b3fd92eb72dad20333449f8e83cfb4a 668bcf60beb005a35354a201dab36bda c8a64537a0b3a93fcde3cdad9f1ce58b ae2d8a571e03ac9c9eb76fac45af8e51 c8a64537a0b3a93fcde3cdad9f1ce58b 16bd032100975551547b4de89daea630 26751f67a3cbb140b1808cf187a4f4df 30c81c46a35ce411e5fbc1191a0a52ef 26751f67a3cbb140b1808cf187a4f4df 36d42170a312871947ef8714799bc5f6 c04b05357c5d1c0eeac4c66f9ff7f2e6 f69f2445df4f9b17ad2b417be66c3710

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Methods and Techniques.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about KMP KMS STATE TABLE (SLAVE)? (Part 2) According to Secure Data Network Systems (SDNS) Key Management Documents, KMP KMS STATE TABLE (SLAVE): | WFJREKEYrsp | | | | | | | | RKRS SLAVE KEYED | ESTAT SLAVE_KEYED | IDLE | |---------------|-------------|------------------|--------------|------------------|------------------|-------------------|------------------------|--------------------|---------------------|------------| | WF_CRLrsp | | | | | CRRS SLAVE KEYED | ESTAT SLAVE_KEYED | | | | IDLE | | SLAVE_KEYED | | | | CRLind WF_CRLrsp | | | IREKEYind WF_IREKEYrsp | | | IDLE | | WF_EXCrsp | | NKRS SLAVE_KEYED | A-ABORT IDLE | | | | | | | IDLE | | DOSSV 3AV1S | EXCind | WF_EXCrsp | | | | | | | | IDLE | | IDLE | SLAVE_ASSOC | | | | | | | | | IDLE | | | ASSOC_RESP | EXCrsp + | EXCrsp- | CRRQ | CRLrsp + | CRLrsp- | RKRQ | IREKEYrsp + | IREKEYrsp- | ASSOC_TERM | KMP STAGED REKEY STATE TABLE (USER) | WF_SRDRS | | | | | | | | SDLIVRcnf MSTR SRKEY | SDLIVRcnf- MSTR_SRKEY | IDLE | |--------------|------------|---------------------|-------------------------|----------------------|--------------|-------------------|-------------------------|------------------------|-------------------------|-----------| | WF_CRRS | | | | | | CRLcnf MSTR_SRKEY | | | CRLcnf- MSTR_SRKEY | IDLE | | WF_SRKRS | | | | SREKEYcnf MSTR_SRKEY | | | | | SREKEYcnf- MSTR_SRKEY | IDLE | | MSTR_SRKEY | | | SRKRQ

Explanation: NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Effective Use of Computing Technology in Vote-Tallying say about 1. Ballot Reconciliation? (Part 1) According to Effective Use of Computing Technology in Vote-Tallying, 1. Ballot Reconciliation: 1. Ballot Reconciliation An important aspect of the supporting documentation is data demonstrating ballot reconciliation. This implies a numerical balance between the number of ballots printed and distributed to precincts and the sum of all uses to which they were pit. Figure 2 demonstrates the flow of ballots in a typical, but not necessarily universal type of election. The following is a description of this typical ballot flow. <!-- image --> actually printed must equal the number ordered. Control documentation is needed at this point. Of all those printed, most are distributed to precincts and absentees and the remainder are sent to central headquarters for possible later use. Control documentation is needed for each precinct's receipts At each precinct, the ballots are either voted unchallenged, voted challenged, spoiled, or unused. Ballots are returned to central headquarters where two reconciliations for each precinct can be made. First, the number of voted ballots (of each individual type, in case each voter is issued more than one type), challenged and unchallenged, must equal the number of voters recorded as having been issued ballots. Second, the number of ballots received at the precinct must equal the number returned from the precinct in all categories. The number of absentee ballots issued and the number returned must be noted for future reconciliations before the returned absentee ballots are dispersed into various counting categories. All unchallenged voted ballots are then inspected for machinereadability before being machine counted. Chad removal from punch-card ballots, according to pre-determined regulation, occurs at this point. Some ballots are approved for computer (or summ?rizer) input as is, and the remainder need to be duplicated. Disagreement at this point as to exactly how a ballot should be duplicated sends the ballot to the challenge process. In the duplication process, the originals are added to the "spoiled" total.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Effective Use of Computing Technology in Vote-Tallying.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-62443 in Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective? (Part 19) Control EC-62443: egime, or closely regulated. Since the Internet was privatized in 1993, the USG has generally practiced a laissez faire approach to Internet standards development, allowing the private-sector to lead. Government experts participate in the IETF when they are working on a discrete need, but generally there has been little coordination of USG participants at IETF meetings to strategically track standards development that can impact national and economic security equities. In many cases, companies would be inhibited from sharing certain information with one another due to protection of proprietary information and antitrust and other rules within the United States. However, there has also been limited outreach on the side of the government to industry partners to discuss ways of coordinating before meetings on areas that have the potential to impact national security equities. Participants, whether corporate or government, produce their own trip reports, but, these reports are not shared within USG or synthesized to create a holistic picture of all relevant activities and working groups at the IETF, which number in the hundreds. This lack of coordination, which can be inherent for other individual member-based SDOs, means that participants act in isolation, and potentially against each other. Although this is appropriate in many commercial circumstances, there may be times when the USG may feel the need to leverage its U.S. industry counterparts within the IETF context to promote, shift, or eliminate a development that could have the potential to impact issues of national significance. ## Case Study - ISO An ISO standard is expected to take two to four years from inception to publication primarily due to the time required to develop international consensus on positions. The national body process treats larger and smaller countries equally.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain D.1.5 ECC P-256 Issuing CA Certificate according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, D.1.5 ECC P-256 Issuing CA Certificate: Serial Number : 4 Signature Algorithm : sha384WithRSAEncryption Issuer : CN=Test Trust Anchor for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US Validity : Not Before: Aug 5 08:30:00 2010 GMT, Not After: Dec 31 08:30:00 2040 GMT Subject : CN=Test ECC P-256 CA for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US Subject Public Key Info : id-ecPublicKey, P-256

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security in ISDN say about 5.1.1 Security Protocols above ISDN? (Part 1) According to Security in ISDN, 5.1.1 Security Protocols above ISDN: 5.1.1 Security Protocols above ISDN As described in section 5.1.2 above, SDNS defines several security protocols which are suitable for use with the OSI and DoD protocol stacks above ISDN at layers 3 and 4. These protocols are above ISDN proper, but are associated with ISDN, when ISDN is used as a part of the OSI (or DoD) protocol stacks. They are expected to provide a starting point for the development of OSI standard security protocols, or similar protocols will be developed for OSI security at layers 3 and 4. Figure 5, above, illustrates the locations of the specific SDNS protocols, which are located above ISDN at layers 3 and 4. The specific variants of the SDNS SP4 and SP3 protocols are discussed in table 1 above. In this section we will simply use "SP3" to mean an OSI network layer security protocol standard and "SP4" to mean an OSI Transport layer security protocol standard, without necessarily meaning a specific SDNS protocol as presently defined. Figure 15 - Transport Layer End-to-End Encryption. <!-- image --> Where an OSI packet data stack utilizes ISDN to provide at least some (but not necessarily all) of the network layer connections, a Transport layer security protocol, such as SP4, can provide a powerful end-to-end confidentiality solution. This solution is illustrated in figure 15 for a B channel connection to a packet network, however it is equally applicable to D channel packet user data services. In figure 15 the packet networic may be implemented by packet handlers in the local office switch, or it may be an independent network reached through the circuit switch. The packet network may in fact be a LAN, or some other network which is entirely independent of ISDN. An intruder monitoring the U interface point sees the Network layer headers as plaintext and the Transport PDU as ciphertext. Since the Network headers and addresses are plaintext, and the size and frequency of packets are apparent, traffic analysis may be fruitful.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security in ISDN.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-1 in Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events? (Part 117) Control IP-1: ed to restart the computer, do so. <!-- image --> 3. Click I Agree. 4. Select Evaluation License. 5. Select Active Directory Forest Recovery. <!-- image --> 6. Click the > button. 7. Click OK. 8. Wait for the installation to complete. <!-- image --> <!-- image --> 9. Click the > button. <!-- image --> 10. Click Finish. 11. There should now be a shortcut on the desktop linking to the web console for Semperis ADFR. 12. On the login page, enter the full domain as well as the NetBIOS name. 13. Enter the username and password of an administrator on the domain. <!-- image --> 14. Click Login. 15. Check the box next to any domain controllers that should be backed up. 16. Click Run Action. <!-- image --> 17. Enter the password in the prompt. 18. Click OK. 19. Click Close. 20. After the installation finishes, click Login at the top of the page. <!-- image --> <!-- image --> 21. Enter the login credentials for the domain. 22. Click Login. 23. Create a recovery password . (Note: In the event of a restoration, Active Directory will potentially be unavailable, so a separate password that is not domain-associated is needed here for restorations.) <!-- image --> <!-- image --> 24. Set recovery questions for the password. 25. Click Set. ## 2.9.2 Create a Backup Schedule for the Domain Controller 1. Click the Backup Settings tab. 2. Enter a name for the rule. 3. Select the days and times that the domain controller should be backed up. 4. Enter the maximum number of backups that should be kept. (Note: The oldest backup will be deleted upon creation of a new backup, which would exceed this maximum.) 5. Ensure that Encrypt and Rule enabled are both turned on. <!-- image --> 6. Click Add Backup Group. 7. Click Create new Backup Group. 8. Enter a name for the backup group. 9. Select the domain controllers to be part of the backup group. <!-- image --> <!-- image --> ## 10. Click OK. 11. Select the newly created backup group. 12. Click OK.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Property Management Systems say about Appendix F References? (Part 2) According to Securing Property Management Systems, Appendix F References: Standards and Technology (NIST). Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1. Apr. 16, 2018. Available at - [9] Joint Task Force Transformation Initiative, Security and Privacy Controls for Information Systems and Organizations, NIST Special Publication (SP) 800-53 Rev. 5, NIST, Gaithersburg, Md., Sept. 2020. Available at - [10] P. Grassi et al., Digital Identity Guidelines, NIST SP 800-63-3, NIST, Gaithersburg, Md., June 22, 2017. Available at - [11] R. Petersen et al., Workforce Framework for Cybersecurity (NICE Framework), NIST SP 800-181 Revision 1, NIST, Gaithersburg, Md., Nov. 2020. Available at - [12] National Institute of Standards and Technology. NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0. Available at .0.pdf. - [13] S. Rose et al., Zero Trust Architecture , NIST SP 800-207, NIST, Gaithersburg, Md., Aug. 2020, 59 pp. Available at - [14] Abbasi et al., 2019 Trustwave Global Security Report , 2019 Trustwave Holdings, Inc. Available at - [15] *NIST. Risk Management Framework: Quick Start Guides . Available at - [16] Joint Task Force, Risk Management Framework for Information Systems and Organizations , NIST SP 800-37 Revision 2, NIST, Gaithersburg, Md., Dec. 2018. Available at

Explanation: NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Securing Property Management Systems.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 915) vailable free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description My-controller: sensor ] python udpping.py --client --npings 6 --host laptop2 --port 4000 start ... Namespace(bind=False, client=True, host='laptop2', npings=6, port=4000, quiet=False, server=False, timeout=False) PING 1 03:31:59 RTT = 1.24670505524 PING 2 03:32:00 RTT = 0.812637805939 PING 3 03:32:01 RTT = 0.652308940887 PING 4 03:32:02 RTT = 0.784868001938 PING 5 03:32:02 RTT = 0.573136806488 PING 6 03:32:03 RTT = 0.481912136078 [rc=6] Manufacturer: sensor ] wget anotherman:800 --2019-07-21 05:23:07-- Resolving anotherman (anotherman)... 10.0.41.245 Connecting to anotherman (another- man)|10.0.41.245|:800... connected. HTTP request sent, awaiting response... 200 OK Length: 116855 (114K) [text/html] Saving to: ‘index.html.1’ index.html.1 100%[================================================ =====================================>] 114.12K --.- KB/s in 0.1s 2019-07-21 05:23:08 (816 KB/s) - ‘index.html.1’ saved [116855/116855] 5. Local-network, controller, my-controller, manufacturer class (in- gress)—blocked: Local-network: NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 425 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description laptop ] wget sensor:888 --2019-05-10 07:47:18-- Resolving sensor (sensor)... 10.0.41.190 Connecting to sensor (sensor)|10.0.41.190|:888... ^C laptop ] wget sensor:888 --timeout 30 --tries 2 --2019-05-10 07:47:29-- Resolving sensor (sensor)... 10.0.41.190 Connecting to sensor (sensor)|10.0.41.190|:888... failed: Connection timed out. Retrying. --2019-05-10 07:48:00-- (try: 2) Connecting to sensor (sensor)|10.0.41.190|:888... failed: Connection timed out. Giving up.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Doug Montgomery according to NIST Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Doug Montgomery: Advanced Network Technologies Division Information Technology Laboratory

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 45) Control EP-67: Maturity Level) can be relatively easy or difficult to ascertain. The Maturity Levels are described in Table 6. The listing is sorted by Core Area of Cybersecurity, then by SDO, and last by Documents. Table 7 - Cryptographic Techniques Standards Cryptographic Techniques: Techniques and mechanisms and their associated standards are used to provide: confidentiality; entity authentication; non-repudiation; key management; data integrity; trust worthy data platforms; message authentication; and digital signatures. | Documents | SDO | Description | Maturity Level (Table 6) | |--------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| | Bluetooth LE | Bluetooth SIG | Bluetooth Low Energy (BLE) A BLE beacon is a small device - usually powered by battery or USB - that emits a Bluetooth Low Energy signal.

Explanation: NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examples of Controls Contained in Rules of Behavior according to NIST Guide for Developing Security Plans for Federal Information Systems According to Guide for Developing Security Plans for Federal Information Systems, Examples of Controls Contained in Rules of Behavior: - Delineate responsibilities, expected use of system, and behavior of all users. - Describe appropriate limits on interconnections. - Define service provisions and restoration priorities. - Describe consequences of behavior not consistent with rules. - Covers the following topics: - o Work at home - o Dial-in access - o Connection to the Internet - o Use of copyrighted work - o Unofficial use of government equipment - o Assignment and limitations of system privileges and individual accountability - o Password usage - o Searching databases and divulging information. Figure 2: Rules of Behavior Examples

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Developing Security Plans for Federal Information Systems.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security Requirements for Controlled Unclassified Information provide? (Section 24) sers] Source Assessment Procedures: AC-06(09), AC-06(10) Determine if: A.03.01.08.ODP[01]: the number of consecutive invalid logon attempts by a user allowed during a time period is defined . A.03.01.08.ODP[02]: the time period to which the number of consecutive invalid logon attempts by a user is limited is defined . A.03.01.08.ODP[03]: one or more of the following PARAMETER VALUES are selected: {the account or node is locked automatically for <A.03.01.08.ODP[04]: time period>; the account or node is locked automatically until released by an administrator; the next logon prompt is delayed automatically; the system administrator is notified automatically; other action is taken automatically}. A.03.01.08.ODP[04]: the time period for an account or node to be locked is defined (if selected) . A.03.01.08.a: a limit of <A.03.01.08.ODP[01]: number> consecutive invalid logon attempts by a user during <A.03.01.08.ODP[02]: time period> is enforced. A.03.01.08.b: <A.03.01.08.ODP[03]: SELECTED PARAMETER VALUES> when the maximum number of unsuccessful attempts is exceeded. [SELECT FROM: access control policy and procedures; procedures for unsuccessful logon attempts; system design documentation; system audit records; system configuration settings; system security plan; other relevant documents or records] [SELECT FROM: personnel with information security responsibilities; system developers; system administrators] [SELECT FROM: mechanisms for implementing the access control policy for unsuccessful logon attempts] Source Assessment Procedure: AC-07 Determine if: A.03.01.09: a system use notification message with privacy and security notices consistent with applicable CUI rules is displayed before granting access to the system.

Explanation: NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 743) operations. 8.6.3 Infrastructure Interdependency Issues Maintaining the resiliency and continuous availability of the power grid itself as a critical national infrastructure is an important mandate. There are also other such critical national infrastructure elements, such as telecommunications, oil and natural gas pipelines, water distribution systems, etc., with as strong a mandate for resiliency and continuous availability. However, the unique nature of the electrical grid is that it supplies key elements toward the operation of these other critical infrastructure elements. Additionally, there are reverse dependencies emerging on smart grid being dependent on the continuous well-being of the telecommunications and digital computing infrastructure, as well as on the continuing flow of the raw materials to generate the power. These interdependencies are sometimes highly visible and obvious, but many remain hidden below the surface of the detailed review for each. There is little current understanding of the cascading effect outages and service interruptions might have, especially those of a malicious and judiciously placed nature with intent to cause maximum disruption and mass chaos. Research into interdependency issues would investigate and identify these dependencies and work on key concepts and plans toward mitigating the associated risks from the perspective of the smart grid. Such research should lead to techniques that show not only how communication failures could impact grid efficiency and reliability, how power failures could affect digital communications, and how a simultaneous combination of failures in each of the systems might impact the system as a whole, but should also apply a rigorous approach to identifying and highlighting these key interdependencies across all of these critical common infrastructure elements.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of Federal Agency Needs for Information Technology Security provide? (Section 79) ' 'sensitive application/ and 'sensitive system." These laws and directives offer latitude to the agency in applying the definitions. As in other areas, the principles are understood at a high level. However, there is much confusion, uncertainty, and frustration as to how they should be applied in specific situations, or when they should be applied, how one knows if it has been done correctly, and who certifies as to the correctness. Many of the interviewees expressed a need for clearer definitions that are easier to apply In their environments. Some felt examples of how these terms are to be applied In real-world situations would be helpful. Some of those interviewed felt they were constantly in the position of being second-guessed. They were uncertain about how much security was needed and how to justify what they implemented. This is also related to some other notions and definitions of 'system" and 'ownership" and 'responsibility" and "due care." Questions included: What is a system?; Is it the hardware or the software or the data or the communications?; What is ownership?; What does ownership imply or entail?; and What are the limits of responsibility? Although the message about the need for standard definitions relating to "sensitive" was clear, interviewees differed with respect to the organizational level (i.e., federal, agency, organization unit) at which this should be done. Many felt levels of sensitivity (and corresponding protections) are a function of the specific agency mission and environment. Some issues identified in the Interviews as directly related to the definitions of 'system" and "sensitive" are: 1) determining appropriate controls for each defined system, and 2) certifying a system is adequately protected (including selecting a basis for certification).

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 49) Control PD-12: | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | |----------------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Applicability | Source | | Preparation and Maintenance of Documentation | DO(DC):1 | The organization develops and implements an issuer operations plan according to the template in Appendix D.2.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Record-Level Requirements and Assertions? (Part 82) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Record-Level Requirements and Assertions: | 3 | | Table_18 | 15.1.13 | The field value shall be selected from Table 18. | 1 | M | Table_18::10.013 | {10.013} MO[0, 1, 10, 11, 12, 13, 14, 15, 20, 30, 40, 50, 51] | 5 | | 10.003::IMT=FACE_ SAP_Mandatory | 15.1.13 | Field 10:013, the Subject Acquisition Profile (SAP), is mandatory when field 10.003 contains "FACE'. | 2 | M | 10.003::IMT=FACE_ SAP_Mandatory | Field 10:013, the Subject Acquisition Profile (SAP), is mandatory when field 10.003 contains "FACE'. | | | RESERVED_FIELDS | 15.1.14 | Fields 10.014 and 10.015 are reserved for definition and inclusion in future revisions of this standard.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.03.08.a[01]: audit information is protected from unauthorized access, modification, and deletion. A.03.03.08.a[02]: audit logging tools are protected from unauthorized access, modification, and deletion. A.03.03.08.b: access to management of audit logging functionality is authorized to only a subset of privileged users or roles.

Explanation: NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches? (Part 111) Control DS-3: the Helix Comm Broker. (Note that putting a single '@' symbol here indicates UDP. Use two, such as '@@' for TCP.) 24. Create a file /etc/rsyslog.d/forcefield.conf and enter the following lines in it. ``` sftp administrator@forcefield.dc.ipdrr:/ForceField.log /tmp/ForceField.log ``` ``` Crontab -e ``` ``` 0 * * * * sftp administrator@forcefield.dc.ipdrr:/ForceField.log /tmp/ForceField.log ``` ``` *.* @192.168.1.206:514 ``` ``` sudo nano /etc/rsyslog.d/forcefield.conf $ModLoad imfile $InputFilePollInterval 10 ``` ``` $PrivDropToGroup adm $InputFileName /tmp/ForceField.log $InputFileTag FORCEFIELD $InputFileStateFile Stat-FORCEFIELD $InputFileFacility local8 $InputRunFileMonitor $InputFilePersistStateInterval 1000 ``` ## 25. Restart rsyslog. sudo service rsyslog restart ## 2.13 Integration: FireEye Helix and Dispel In this integration, we configure the collection of logs from Dispel, our network protection solution. Because Dispel controls access from users to enterprise systems, it is important to have an overview of its actions through log collection and reporting. Dispel personnel can perform this integration by simply providing them with the protocol, port, and IP address of the Helix Communications Broker and allowing them to configure it on the on-premise Dispel wicket. ## 2.14 Integration: Avrio SIFT and PKWARE PKProtect When used together, SIFT and PKProtect can protect sensitive data accidentally dropped into public shares on the enterprise. In Section 2.6, we detail how to configure SIFT to detect sensitive data in a Windows Share and move it to a location designated for sensitive information. Now, we will demonstrate how to ensure that location is protected by PKProtect, which will automatically encrypt the data. ## 2.14.1 Configuring PKWARE PKProtect 1. Navigate to the PKProtect dashboard and login. 2. Navigate to Archive > Discovery . <!-- image --> 3. Click Pattern - Dictionary . 4. Enter a name for these patterns in the Name field. 5.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2011 Annual Report say about Policy Machine? (Part 3) According to Computer Security Division 2011 Annual Report, Policy Machine: ternational Committee for Information Technology Standards (INCITS) working group continued development of a three-part PM standard under the title of 'Next Generation Access Control' (NGAC). This work was conducted under three sub-projects: - Project 2193-D: Next Generation Access Control Implementation Requirements, Protocols and API Definitions; - Project 2194-D: Next Generation Access Control Functional Architecture; and - Project 2195-D: Next Generation Access Control Generic Operations & Abstract Data Structures. In the coming year, we anticipate conducting a demonstration of the Cloud PM implementation, and bringing parts of the NGAC proposed standard to ballot by INCITS. We expect that this project will: - Offer users capabilities of a variety of services achieved through configuration of PM data alone, such as file management, email, workflow, and forms and records management, rather than managing overlapping user accounts, and potentially different authentication schemes for each data service, through a single authenticated session; - Deliver to select users, through the policy machine, select capabilities (of different services) under combinations of arbitrary, but mission-tailored forms of discretionary, mandatory, and history-based access controls, rather than deploying and managing different access control schemes for different data services; - Provide an inherent property of the PM, the comprehensive nature in which data services interplay. For instance, a user can attach a record, created under a relational database management service, to an email message and send that record to any chosen individual.

Explanation: NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Computer Security Division 2011 Annual Report.