Key usage history management

Prev Next

Available in Classic and VPC

Cryptographic key usage history

Cryptographic key usage history plays a crucial role in meeting security audit and compliance requirements. Key Management Service logs usage history for all requests processed for keys. By default, usage history is provided as follows:

Before feature update After feature update
History storage policy Stores all history from key creation to deletion. Stores up to 30,000 records of history for the most recent 30 days.
(If requests exceed 30,000 within 30 days, the oldest request records are sequentially deleted.)
History provision method Provides the most recent 100 records via console (earlier records can be requested separately through Customer Center). Real-time access to up to 30,000 records for the past 30 days (console and APIs).
History deletion point Maintained for 1 year after key is deleted, then destroyed. Immediately destroyed at the time when the key is deleted.
Policy effective date Effective until November 30, 2024. Effective from December 1, 2024.
Example: On January 1, 2025, the key usage history from December 1, 2024, is deleted.

View key history

To protect against a variety of security threats, you can view the full usage history of your keys to monitor whether they're being used appropriately. To view the key usage history:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Security > Key Management Service > Key.
  2. Click to select the key for which you want to view the usage history, and then move to the [Usage history] tab.
  3. Check the request history by setting the period you want to review. You can search usage history by entering keywords you want to check.
    kms-activity_01(1)_ko
    • Request time: The time when the request was processed.
    • Request type: Distinguishes whether the request was made through the console or API.
    • IP (or Hostname): The IP address from which the request was sent. IP ACL is processed based on this address.
    • Requester (ID): The account ID of the requester's Sub Account is recorded. For tokens, the token issuer's ID is recorded.
    • Action: The requested APIs are recorded.
    • Response content: Records whether the response was successful or failed. (Response body contents are not recorded.)

Integrate with Cloud Log Analytics

When integrated with Cloud Log Analytics, you can also view the key usage history from the console. To integrate with Cloud Log Analytics:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Security > Key Management Service > Key.
  2. Click to select the key for which you want to view the usage history, and then move to the [Usage history] tab.
    • For keys that are not integrated with Cloud Log Analytics, the Set CLA integration button is displayed.
  3. Click Set CLA integration. Integration is completed.
    kms-activity_02_ko
    • For users who are not using Cloud Log Analytics, you need to subscribe to Cloud Log Analytics first. Click Subscribe to Cloud Log Analytics. When the service application is completed, the integration is completed successfully.
  4. If you no longer want to integrate with CLA, click Cancel CLA Integration. The integration is canceled immediately.
Note

Even if you cancel the Cloud Log Analytics integration, the history records stored in Cloud Log Analytics before the cancellation is maintained.