daclark's WebLog

Your comments read like a security review and risk analysis. We do not have any public documentation available to help you here. Our security model is based on the trusted subsystem, only authenticated users are allowed to make authorized requests, but once the request is authorized, the service will fire. This is why approval and audit actions are so important. As another layer (if you don't support delegation, you could validate ProvisioningRequests where the calling user and the logged user do not match. In the end, we're only as secure as the environment deployed (one of the reasons MS Services is involved). As for suspicious activity, you might want to use MOM to catch multiple service requests executed by the same user. Your final question suggests that you'd like ZTP to be the authoritative audit source for a connected endpoint. This is a common request when using MIIS integration. The convergence engine of MIIS allows us to log changes to the Connector Space and then synch from the MetaVerse with the appropriate attribute flow. Some changes could be disallowed (restored on next run), while others could be flagged for audit, causing a workflow for approval or security notification. I hope this was helpful and recommend that you work with Microsoft Services to help you better understand the solution with your needs in mind and scope the effort.