
Last updated: 2026-11-16
Check your exposure, then assign the right owner. The Pegasus breach notice gives IT a reason to review who owns privileged accounts. Apify customers have a more immediate question about their own accounts and data. Teams that use or sell automated hiring tools have a planning task for 2027.
Türkiye’s data protection authority published the Pegasus breach notice on 11 November. Pegasus reported that someone used an administrator password to access its IT request and development system without authorization. Pegasus had yet to establish how the password was obtained. The company reported that the incident affected the identity and contact data of 11,762 employees and users. The authority’s review was ongoing when it published the notice.
Check this week. Pick one system that handles personal data, such as a support desk or an internal request portal. Ask the system owner to verify who holds admin access, whether each account still needs it and whether the logs can tie privileged activity to an individual.
Apify disclosed the incident on 11 November and posted its latest public update on 13 November. The vendor reported unauthorized access to some customer accounts. It said on 12 November that it had emailed customers whose personal information or stored data it had identified as accessed. If you received no email, Apify said it had not identified your account as affected at that point. Apify’s investigation was still open as of the 13 November update.
Check now if you use Apify. Ask the account owner to look for a direct notice and follow the instructions for the affected account. Check what data your workflows send to Apify and which integrations they use. Apify also advised all users to restrict access to their storage. If your team has no direct or indirect Apify exposure, this incident calls for monitoring at most.
On 11 November, the European Data Protection Board selected automated decision-making in recruitment, including AI-driven screening, for its 2027 coordinated enforcement action. The announcement sets a focus for enforcing existing GDPR rights, including the right of access and protections around solely automated decisions that have legal or similarly significant effects. The topic selection itself leaves existing obligations unchanged. Any findings would come from the enforcement work.
Plan if this applies to you. Employers whose screening falls within the GDPR and vendors selling screening tools to EU employers can start by mapping where a tool ranks, rejects or advances a candidate. Walk through one application from submission to decision. Record who can override the outcome and what information the employer can retrieve if the candidate asks for access.
Controller report · Pegasus
Owner IT or security lead
Action Verify admin ownership on one system.
Monitor only Follow the public notice if you are tracking the Pegasus investigation.
Vendor disclosure · Apify
Owner Apify account owner
Action Check direct notices and identify the workflows or data in scope.
Monitor only If you have no direct or indirect exposure, no incident response is needed.
Future enforcement focus · Automated recruitment
Owner HR or hiring-product lead, with privacy support
Action Trace one screening decision and identify who can override it.
Monitor only If you neither use in-scope screening nor supply it to EU employers, follow the regulator’s updates as relevant.
If vendor notices or regulatory updates routinely reach the wrong team, Kooch’s Ongoing Compliance Management can help define who receives them, who makes decisions and when to escalate.