Typically, anti-cheat is separated into a frontend and a backend. The frontend becomes active at an enumerated set of events/criteria and collects data (screenshots, keystrokes, directory listings, process lists, results of memory scans, if instructed by the backend also memory contents or file contents) to the backend for further analysis.
These criteria are often ad-hoc (such as "if processes are running out of a user directory, capture them") and usually accumulate over time.
Typically, anti-cheat is separated into a frontend and a backend. The frontend becomes active at an enumerated set of events/criteria and collects data (screenshots, keystrokes, directory listings, process lists, results of memory scans, if instructed by the backend also memory contents or file contents) to the backend for further analysis.
These criteria are often ad-hoc (such as "if processes are running out of a user directory, capture them") and usually accumulate over time.