An organisation is documenting who owns which security controls on its hosted production instance, and needs the split that the ServiceNow shared responsibility model describes. Which pairing assigns responsibility correctly?
- AServiceNow defines the role hierarchy used by each application on the instance, while the customer maintains the network hardware that carries traffic to it.
- BServiceNow maintains the data centre facilities and the platform software beneath the instance, while the customer defines the roles and access control rules that govern record access. Correct
- CServiceNow classifies the business data loaded into the instance tables, while the customer patches the operating system and database software that the instance runs on.
- DServiceNow configures the instance security settings once the customer has gone live, while the customer arranges redundancy between the paired hosting data centres.
Why A is wrong: Tempting because ServiceNow does ship baseline roles with each application, but the customer decides which roles exist for its own applications and who holds them, and the customer never touches the hosting hardware.
Why B is correct: Correct, because the vendor owns everything from the physical facility up to the running platform, and the customer owns what it configures on top of that platform, access control being the clearest example.
Why C is wrong: Tempting because both activities are genuinely necessary, but each sits on the wrong side: only the customer knows the sensitivity of its own data, and the customer has no access to the hosting stack to patch it.
Why D is wrong: Tempting because ServiceNow does supply security guidance at go live, but instance configuration remains customer work, and data centre pairing and failover are arranged by the vendor, not the subscriber.