Skip to content

Windows Event ID 5063: A cryptographic provider operation was attempted

Written when an operation on a cryptographic provider is attempted. It captures registration of and operations on cryptographic modules (providers).

Overview

The subcategory is Audit Other Policy Change Events. It is generated when registration or unregistration (BCryptRegisterProvider / BCryptUnregisterProvider) of a cryptographic provider (a module implementing cryptographic algorithms; CSP/KSP, etc.) is attempted. There are success (S) and failure (F) variants.

How it is triggered

  • Registration or unregistration of a cryptographic provider.

Security review points

  • Registering a rogue cryptographic provider can insert a custom module into the authentication/crypto path and be used for credential theft or a backdoor (a concern similar to SSP/authentication packages 4610/4622). Note unexpected provider operations.
  • Together with related crypto provider registration events (the 5064-5070 family), track changes to the provider configuration.

Notes for log review

  • It is normally rare. Know the legitimate components that register/change cryptographic providers and check operations by anything else.
  • Investigate registration/operation of unfamiliar providers at high priority.

MITRE ATT&CK mapping

No technique maps directly. Rogue crypto provider registration is reviewed as tampering with the authentication path (the same concern as T1547.005 Security Support Provider).

Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.

Key fields

FieldMeaning
Provider NameThe cryptographic provider in question
OperationThe operation type
SubjectThe acting subject

References