Control statement
- a.Prohibit [Organization-defined: sc-42_odp.01] ; and
- b.Provide an explicit indication of sensor use to [Organization-defined: group of users].
Discussion
Sensor capability and data applies to types of systems or system components characterized as mobile devices, such as cellular telephones, smart phones, and tablets. Mobile devices often include sensors that can collect and record data regarding the environment where the system is in use. Sensors that are embedded within mobile devices include microphones, cameras, Global Positioning System (GPS) mechanisms, and accelerometers. While the sensors on mobiles devices provide an important function, if activated covertly, such devices can potentially provide a means for adversaries to learn valuable information about individuals and organizations. For example, remotely activating the GPS function on a mobile device could provide an adversary with the ability to track the movements of an individual. Organizations may prohibit individuals from bringing cellular telephones or digital cameras into certain designated facilities or controlled areas within facilities where classified information is stored or sensitive conversations are taking place.
Organization-defined parameters
These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.
From control text to operational evidence
Use Sensor Capability and Data as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to secure architecture, boundary protection, communications protection, cryptography, and system isolation.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- network and trust-boundary diagrams
- firewall and gateway configurations
- cryptographic configuration and key records
- segmentation and isolation test results
Common failure patterns
- diagrams omit cloud and third-party paths
- encryption enabled without key governance
- flat trust zones allow unnecessary lateral movement
- boundary rules accumulate without owner review
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
- SC-42a.[Organization-defined: sc-42_odp.01] is/are prohibited;
- SC-42b.an explicit indication of sensor use is provided to [Organization-defined: group of users].
Examine
- System and communications protection policy
- procedures addressing sensor capabilities and data collection
- access control policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system audit records
- system security plan
- privacy plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security and privacy responsibilities
- system developer
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel responsible for sensor capabilities
Test
- Mechanisms implementing access controls for the remote activation of system sensor capabilities
- mechanisms implementing the capability to indicate sensor use
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Control enhancements
Enhancements add specificity, strength, or scope to the base control. Baseline badges show explicit selections in the official SP 800-53B OSCAL profiles.
SC-42(1) — Reporting to Authorized Individuals or Roles
Verify that the system is configured so that data or information collected by the [Organization-defined: sensors] is only reported to authorized individuals or roles.
Official discussion
In situations where sensors are activated by authorized individuals, it is still possible that the data or information collected by the sensors will be sent to unauthorized entities.
Organization-defined parameters (1)
Assessment objectives and methods
the system is configured so that data or information collected by the [Organization-defined: sensors] is only reported to authorized individuals or roles.
Examine
- System and communications protection policy
- access control policy and procedures
- procedures addressing sensor capability and data collection
- personally identifiable information processing policy
- system design documentation
- system configuration settings and associated documentation
- system architecture
- system audit records
- system security plan
- privacy plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security and privacy responsibilities
- system developer
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel responsible for the sensor capabilities
Test
- Mechanisms restricting the reporting of sensor information to those authorized
- sensor data collection and reporting capabilities for the system
SC-42(2) — Authorized Use
Employ the following measures so that data or information collected by [Organization-defined: sc-42.01_odp] is only used for authorized purposes: [Organization-defined: measures].
Official discussion
Information collected by sensors for a specific authorized purpose could be misused for some unauthorized purpose. For example, GPS sensors that are used to support traffic navigation could be misused to track the movements of individuals. Measures to mitigate such activities include additional training to help ensure that authorized individuals do not abuse their authority and, in the case where sensor data is maintained by external parties, contractual restrictions on the use of such data.
Organization-defined parameters (1)
Assessment objectives and methods
[Organization-defined: measures] are employed so that data or information collected by [Organization-defined: sc-42.01_odp] is only used for authorized purposes.
Examine
- System and communications protection policy
- access control policy and procedures
- personally identifiable information processing policy
- sensor capability and data collection
- system design documentation
- system configuration settings and associated documentation
- system architecture
- list of measures to be employed to that the ensure data or information collected by sensors is only used for authorized purposes
- system audit records
- system security plan
- privacy plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security and privacy responsibilities
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel responsible for sensor capabilities
Test
- Mechanisms supporting and/or implementing measures to ensure that sensor information is only used for authorized purposes
- sensor information collection capability for the system
Related controls
SC-42(3) — Prohibit Use of Devices
This enhancement is marked withdrawn in the official OSCAL catalog. Related-control metadata below may identify where its intent was incorporated.
SC-42(4) — Notice of Collection
Employ the following measures to facilitate an individual’s awareness that personally identifiable information is being collected by [Organization-defined: sensors]: [Organization-defined: measures].
Official discussion
Awareness that organizational sensors are collecting data enables individuals to more effectively engage in managing their privacy. Measures can include conventional written notices and sensor configurations that make individuals directly or indirectly aware through other devices that the sensor is collecting information. The usability and efficacy of the notice are important considerations.
Organization-defined parameters (2)
Assessment objectives and methods
[Organization-defined: measures] are employed to facilitate an individual’s awareness that personally identifiable information is being collected by [Organization-defined: sensors]
Examine
- System and communications protection policy
- access control policy and procedures
- personally identifiable information processing policy
- sensor capability and data collection policy and procedures
- system design documentation
- system configuration settings and associated documentation
- privacy risk assessment documentation
- privacy impact assessments
- system architecture
- list of measures to be employed to ensure that individuals are aware that personally identifiable information is being collected by sensors
- examples of notifications provided to individuals that personally identifiable information is being collected by sensors
- system audit records
- system security plan
- privacy plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security and privacy responsibilities
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel responsible for sensor capabilities
Test
- Mechanisms supporting and/or implementing measures to facilitate an individual’s awareness that personally identifiable information is being collected by sensors
- sensor information collection capabilities for the system
Related controls
SC-42(5) — Collection Minimization
Employ [Organization-defined: sensors] that are configured to minimize the collection of information about individuals that is not needed.
Official discussion
Although policies to control for authorized use can be applied to information once it is collected, minimizing the collection of information that is not needed mitigates privacy risk at the system entry point and mitigates the risk of policy control failures. Sensor configurations include the obscuring of human features, such as blurring or pixelating flesh tones.
Organization-defined parameters (1)
Assessment objectives and methods
the [Organization-defined: sensors] configured to minimize the collection of information about individuals that is not needed are employed.
Examine
- System and communications protection policy
- access control policy and procedures
- personally identifiable information processing policy
- sensor capability and data collection policy and procedures
- system design documentation
- system configuration settings and associated documentation
- privacy risk assessment documentation
- privacy impact assessments
- system architecture
- list of information being collected by sensors
- list of sensor configurations that minimize the collection of personally identifiable information (e.g., obscure human features)
- system audit records
- system security plan
- privacy plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security and privacy responsibilities
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel responsible for sensor capabilities
Test
- Mechanisms supporting and/or implementing measures to facilitate the review of information that is being collected by sensors
- sensor information collection capabilities for the system
Related controls
Authoritative sources
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.