From b42c3f3229ab98c280bd0bef547567eee468d2ce Mon Sep 17 00:00:00 2001
From: ikeyan <kik@nvstl.com>
Date: Mon, 15 Dec 2025 12:38:31 +0900
Subject: [PATCH] doc: added 'secure' event to tls.TLSSocket

Fixes #61060
---
 doc/api/tls.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/doc/api/tls.md b/doc/api/tls.md
index 43fa0c990e19b8..58d05203369d6a 100644
--- a/doc/api/tls.md
+++ b/doc/api/tls.md
@@ -951,6 +951,18 @@ The listener callback is passed a single argument when called:
 Typically, the `response` is a digitally signed object from the server's CA that
 contains information about server's certificate revocation status.
 
+### Event: `'secure'`
+
+<!-- YAML
+added: v0.11.4
+-->
+
+The `'secure'` event is emitted after the TLS handshake has successfully
+completed and a secure connection has been established.
+
+This event is emitted on both client and server {tls.TLSSocket} instances,
+including sockets created using the `new tls.TLSSocket()` constructor.
+
 ### Event: `'secureConnect'`
 
 <!-- YAML
@@ -1529,7 +1541,7 @@ changes:
   * `requestCert`
 
 * `callback` {Function} If `renegotiate()` returned `true`, callback is
-  attached once to the `'secure'` event. If `renegotiate()` returned `false`,
+  attached once to the [`'secure'`][] event. If `renegotiate()` returned `false`,
   `callback` will be called in the next tick with an error, unless the
   `tlsSocket` has been destroyed, in which case `callback` will not be called
   at all.
@@ -2456,6 +2468,7 @@ added: v0.11.3
 [TLS recommendations]: https://wiki.mozilla.org/Security/Server_Side_TLS
 [`'newSession'`]: #event-newsession
 [`'resumeSession'`]: #event-resumesession
+[`'secure'`]: #event-secure
 [`'secureConnect'`]: #event-secureconnect
 [`'secureConnection'`]: #event-secureconnection
 [`'session'`]: #event-session