Event 4656 says a process asked for a handle to an object and records what happened to the request. Microsoft's description is that specific access was requested for a file system, kernel or registry object, or a file system object on removable storage or a device. If access was declined, a Failure event is written. Either form generates only when the object's SACL has an entry covering the rights involved. Microsoft is explicit about the limit. The event shows that access was requested and the result of the request, but not that the operation was performed. For that you read 4663.
Four audit subcategories can carry it: File System, Kernel Object, Registry and Removable Storage. They have very different economics. Microsoft states that no events are generated for the default file system SACLs, and its advice for File System and Registry is not to enable them until you have planned how the data will be used. For kernel objects it says the events have little to no security relevance, are hard to parse and need no auditing unless you know exactly what to watch. A policy called "Audit: Audit the access of global system objects" sets the default SACL on kernel objects, so that is the setting to check when kernel-object volume surprises you. A Spiceworks admin counted more than 82 million 4656 events for one user in a month, and the sample in the thread is services.exe requesting access 0x1, "Connect to service controller", on an SC_MANAGER OBJECT named ServicesActive. That is not a file at all.
Only 4656 records refusals. Event 4663 has no failure version, so a refused attempt leaves no trace there. Microsoft's File System page says it directly: Failure events can show you unsuccessful attempts to access specific file system objects. Audit Success and Audit Failure are keyword bits on the event. Microsoft's 4625 sample, a failure event, carries 0x8010000000000000 and its 4624 sample carries 0x8020000000000000.
AccessMask is the access that was requested, which is not the access that was used. Microsoft's own sample is Notepad opening a text file with mask 0x12019f. Break it down with the file right table: ReadData 0x1, WriteData 0x2, AppendData 0x4, ReadEA 0x8, WriteEA 0x10, ReadAttributes 0x80, WriteAttributes 0x100, READ_CONTROL 0x20000 and SYNCHRONIZE 0x100000. Nine rights, and the AccessList field names each of them. Notepad asked for write access to open a file, and nothing in the 4656 says it ever wrote. Treat the requested mask as a ceiling and let 4663 tell you what happened. The simulated event here asks for 0x120089, which is ReadData, ReadEA, ReadAttributes, READ_CONTROL and SYNCHRONIZE: a plain read.
PrivilegeList records which privileges the access check used. Microsoft defines it as the privileges used for the access check, with SeBackupPrivilege as the example, and a hyphen when none were. Microsoft's table says SeBackupPrivilege makes the system grant read access to any file regardless of its ACL. A hyphen means no privilege was involved in the check. Anything else means one was, which is exactly the case where a permissions review says "no access" and the log says the file was read.
The remaining fields are the Subject block, ObjectServer (Security for this event), ObjectType, ObjectName, TransactionId, RestrictedSidCount, ProcessId in hexadecimal and ProcessName. Version 1 on Windows Server 2012 and Windows 8 added ResourceAttributes and AccessReason. Microsoft does not decode the AccessReason codes on the event page, so lean on AccessMask and AccessList for rules and use the rendered text in Event Viewer when you need the reason.
HandleId ties the lifecycle together. A 4656 opens it, a 4663 uses it, and a 4658 closes it, but 4658 only exists if you enable Audit Handle Manipulation, which Microsoft says has little security relevance beyond telling you how long a handle stayed open. Microsoft warns that HandleId can be captured as 0x0, in which case there is nothing to join. The deletion event, 4660, carries only a HandleId and no object name, so the name of a deleted file comes from the 4656 or 4663 with the same handle.
Microsoft's registry page has one wrinkle. On Windows 11 and Windows Server 2022 and later, the 4656 for a newly created subkey appears only under the legacy Audit Object Access setting, and earlier versions do not write it during subkey creation.