In embodiments, the telemetry processing pipeline of STS 232 that generates token 600 incorporates the RPO modeling/requirements noted herein, and is configured to emit sign-in logs or audit reports in both the domain of the user/remote principal and the domain of the data resource owner. As similarly noted above for token generation in flow diagram 400, embodiments provide for the logs/audit reports provided to the domain of the data resource owner to be exclusive of any user-/remote principal-specific information, while the logs/audit reports that are emitted into the domain of the user/remote principal are permitted to include the actual user/remote principal information. In other embodiments, however, portions of principal-specific/identifying information may be included in logs/audit reports based on an agreement therefor between data resource owners and accessors.
Accessing secure data resources, such as directory data, via remote principals is a sensitive operation. Because there are at least two different organizations involved in setting up the access controls, and one organization obtaining the ability to read data of another organization, embodiments herein provide for the sign-in/authentication and all task activity, which are important data for audits, to be tracked to prevent abuse and further reduce the risk of using the described embodiments for conducting tasks and operations on data resources.