Using a bought tool usually makes the employer the controller and the vendor a processor; the employer must comply with the principles, make sure workers and others captured can exercise their rights, choose a processor giving sufficient guarantees, meet accountability duties such as DPIAs and data protection by design and default, decide controller and processor roles before processing starts, and obtain, under a written contract or service agreement, enough information about the tool to meet its responsibilities. A vendor using the data for its own purposes is likely a controller for that processing.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.