Skip to content

Windows Event ID 5061: Cryptographic operation

Written when a cryptographic operation such as opening, creating, or deleting a key is performed through a Key Storage Provider (KSP). It captures key usage and, together with key-related events, lets you track use of credentials and key material.

Overview

The subcategory is Audit System Integrity. It is generated when a cryptographic operation (opening a key, creating a key, and so on) is performed through a KSP. It applies only when the “Microsoft Software Key Storage Provider” or the “Microsoft Smart Card Key Storage Provider” is used. There are success (S) and failure (F) variants, including the provider, algorithm, target key, operation type, return code, and acting account (not the process).

How it is triggered

  • When an application or service performs a cryptographic operation using a key.
  • It occurs when certificates whose keys live in those KSPs (such as TLS server certificates) are used.

Security review points

  • If a specific key (a certificate’s private key, a code-signing key, etc.) is used by an unexpected account, suspect key misuse. Together with key file operation 5058, track the location and use of keys.
  • Because it appears in volume, monitor narrowed to keys and accounts of interest.

Notes for log review

  • It occurs in volume during legitimate cryptographic processing. Full volume always-on is impractical; narrow to use of high-value keys or by accounts that do not normally handle keys.
  • Together with failures 5057/5060, watch for anomalies in cryptographic use.

MITRE ATT&CK mapping

No technique maps directly. If an unexpected account uses a certificate or code-signing private key, suspect key theft (T1552.004 Private Keys).

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

Key fields

FieldMeaning
Key NameThe key used
OperationThe type of cryptographic operation
Subject\Account NameThe acting account

References