# Threat database We use fingerprinting techniques to help customers mitigate attacks before and after they occur. Cyphor will never share the device fingerprint with customers or third parties; the sole purpose of fingerprints is to allow customers to detect and mitigate connections coming from machines that attempted to tamper or used pirated software in the past. The device fingerprint collection does not involve personal or user-identifiable data and is never used for tracking activities. ### Do you use hardware identifiers? Yes. ### Can users reset their fingerprint with a factory reset? No. Our fingerprint is resistant to OS reinstalls. ### Do you store non malicious fingerprints? No, only machines linked to tampering attacks are registered in our databases. ### How reliable is device fingerprinting in virtualized environments? Attackers can easily generate new fingerprints on new deployments. We have a module that detects execution on virtualized environments; however, this solution might not fit applications that need to run on virtual machines. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cyphor.net/code-guard/threat-database.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.