LogoLogo
  • Welcome to Cyphor
  • .NET Code Obfuscation
    • Getting Started
    • How to Obfuscate
    • Basic Code Obfuscation
      • Symbol Renaming
      • Body Mutation
      • Control Flow
      • Constant Encryption
      • Call Hiding
      • Debug Protection
      • Integrity Checks
      • Self Healing
    • Advanced Obfuscation
      • Attribute-Based Obfuscation
      • Guide to obfuscation
      • Code Inlining
      • What is RASP?
      • Protections that protect each other
      • Program not working after obfuscation
      • Keeping performance with obfuscation
      • Virtualization
  • Dashboard
    • Files
    • Billing
      • Pay as you go
      • Examples
    • Projects
      • Code Guard Tasks
      • Permissions
        • Roles
      • Files
      • SAML and SSO
  • Code Guard
    • Introduction
    • Implement with your licensing system
      • Setting up a gateway
      • Setting up the SDK
    • Secured values
      • Dynamic values
      • Code Encryption
        • Page 1
    • Preventing analysis
    • Enhanced visibility
      • Disabling tracing on production
      • Logging external methods
      • Optimizing Memory Usage
    • Edge connectivity
    • Preventing modifications
      • Preventing assembly load
      • Allowing partial tampering
      • Enterprise EDRs and XDRs
      • Dynamic Hook protection
      • Thread hijacking
      • Guard Checksums
      • DLL Injection
      • Handling complex RE attacks
        • Custom payload detection
    • Granular Integrity Checks
    • Virtualized Environments
    • Troubleshooting
    • Threat database
    • Real time alerts
      • Alert Insights
  • CLI Tool
    • Introduction
    • Global options
    • Profiles
    • Projects
    • Obfuscator
      • Obfuscation Schemes
      • Task templates
      • Protecting files
        • Global obfuscation flags
        • Using templates to obfuscate files
        • Quick obfuscation
      • Monitoring obfuscation jobs
    • Securing local storage
Powered by GitBook
On this page
  • Do you use hardware identifiers?
  • Can users reset their fingerprint with a factory reset?
  • Do you store non malicious fingerprints?
  • How reliable is device fingerprinting in virtualized environments?

Was this helpful?

  1. Code Guard

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.

PreviousTroubleshootingNextReal time alerts

Last updated 1 year ago

Was this helpful?