PCI DSS 4.0 2.2.3: 2.2.3 Primary functions with different security levels managed
Where primary functions need different security levels, the entity must manage them in one of three ways: (a) a system component hosts only one primary function; OR (b) co-located primary functions whose security levels differ are isolated from one another; OR (c) co-located primary functions whose security levels differ are all secured to the level demanded by the function with the greatest security need. Applicability: no special notes; applies to every assessed entity. Customized approach objective: a less sensitive primary function cannot weaken the protection of a more sensitive one sharing the same system component.
This control maps to 35 controls across 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 2.2.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.