Anavem
Languagefr
audit policyComputer ConfigurationNot configured

Audit Other Object Access Events

Audits scheduled task creation, COM+ object access, and other object events.

10 May 20264 min
Policy path
Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Object Access
Supported on
Windows 10, Windows 11, Windows Server 2016 and later

Audits scheduled task creation, COM+ object access, and other object events. Security baselines recommend setting it to Success and Failure.

Description

Audit Other Object Access Events is a Windows Group Policy setting located under Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Object Access. It applies to the Computer Configuration branch and is classified as a Informational-level policy in the Advanced Audit Policy category.

Audits scheduled task creation, COM+ object access, and other object events.

Microsoft sets the default value to No auditing while industry security baselines (CIS, NIST, DISA STIG) recommend Success and Failure.

In-depth explanation

This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.

The policy is grouped under Advanced Audit Policy, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

Use cases

  • Apply organization-wide hardening of advanced audit policy on all domain-joined Windows endpoints.
  • Roll out a CIS Benchmark-aligned baseline targeting 'Audit Other Object Access Events' via a dedicated GPO.
  • Reduce attack surface for accounts that handle privileged credentials or sensitive data.
  • Standardize the configuration across multiple customer tenants for an MSP-managed fleet.
  • Forward security events to a SIEM (Sentinel, Splunk, Wazuh) for incident investigation.

Security implications

This control is primarily about consistency and supportability rather than security. The main risk of leaving it unconfigured is divergence between machines, which makes troubleshooting and standardized imaging harder, especially across multiple customer tenants in an MSP context.

How to configure

  1. Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
  2. Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – Advanced Audit Policy) instead of editing Default Domain Policy.
  3. Navigate to Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Object Access.
  4. Open Audit Other Object Access Events and set it to Success and Failure.
  5. Click OK and close the editor.
  6. On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Frequently asked questions

What does the Audit Other Object Access Events Group Policy do?
Audits scheduled task creation, COM+ object access, and other object events.
Where do I find this setting in the GPO editor?
Open <code>gpmc.msc</code>, then navigate to <code>Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Object Access</code> and look for <strong>Audit Other Object Access Events</strong>.
What is the Microsoft default value?
<code>No auditing</code> on a fresh Windows install. Domain-joined machines may inherit a different value if a baseline GPO is already in place.
What value do security baselines recommend?
<code>Success and Failure</code> – aligned with CIS, NIST, and DISA STIG guidance for current Windows versions.
How quickly does the change take effect?
After the next Group Policy refresh — run <code>gpupdate /force</code> for immediate testing or wait ~90 minutes for workstations / ~5 minutes for domain controllers. Some computer-side policies require a reboot, and some user-side policies require sign-off/sign-on.