A DSP that lets third-party add-ons connect to its product through an API takes reasonable care that appropriate security controls are in place for its add-on partners, using the Security Standard for Add-on Marketplaces (SSAM) or an equivalent set of controls (SSAM applies to add-on developers with more than 1,000 connections to Australian business customers of a DSP or connected to a tax or BAS agent's practice client list). The DSP provides the security standard it uses to govern add-ons, evidence that partners meet SSAM or its equivalent, and a list of third-party developers with links to their products. SSPs and gateways are not treated as add-on marketplaces.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.