Kiteworks and Cyera have integrated to apply Cyera’s data classifications directly within Kiteworks’ Data Policy Engine, enabling automatic tagging of uploaded files with Cyera classifications for consistent policy enforcement across email, file sharing, SFTP, managed file transfer, APIs, and AI integrations.

Kiteworks highlights a suite of security certifications and compliance credentials, including FedRAMP in progress (High), FedRAMP Moderate Authorized, FIPS 140-3 validation, and SOC 2 Type II, along with compliance reporting for CMMC 2.0, GDPR, and HIPAA.

Additional resources include a solution brief detailing the integration, and an invitation to a Kiteworks dinner at datasecAI by Cyera on November 9 for security, IT, risk, and compliance professionals.

Tim Freestone, Kiteworks Chief Strategy Officer, notes that classifications matter only when acted upon, and the integration ensures Cyera classifications trigger policy evaluations for every access request, including those from machines and AI agents.

To support governance and auditability, Kiteworks logs requested actions, user identities, classification tags, and affected files, and extends governance controls to AI agents through its Compliant AI approach, enabling governed data interactions across sectors like financial services, healthcare, government, manufacturing, and legal.

The Cyera DSPM platform provides AI-native data security posture management and classification capabilities that help identify, prioritize, and mitigate data risks, with classifications extended into Kiteworks’ data exchange environments.

The Data Policy Engine evaluates the file’s classification along with user attributes and requested actions to determine whether access or data exchange is permitted, blocked, restricted, or requires approval, applying to humans, machines, and AI agents alike.

A daily scheduled synchronization process aligns Kiteworks’ records with Cyera’s inventory, removing classifications that are no longer present in Cyera. The integration supports file sources identified by SHA-256 or MD5 hashes.

When a file is uploaded, Kiteworks queries Cyera using a unique file identifier (without disclosing file contents or metadata). If Cyera recognizes the file, its classification is returned and applied as a tag by Kiteworks.