Add DSN utilization

src/docs/product/sentry-basics/dsn-explainer.mdx

@@ -14,6 +14,14 @@ If this value is not provided, SDKs will try to read it from the `SENTRY_DSN` en
 
 If an SDK is not initialized or if it is initialized with an empty DSN, the SDK will not send any data over the network, such as captured exceptions.
 
+### DSN Utilization
+
+DSNs are safe to keep public because they only allow submission of new events and related event data; they do not allow read access to any information.
+
+While there is a risk of abusing a DSN, where any user can send events to your organization with any information they want, this is a rare occurrence. Sentry provides controls to [block IPs](/platform-redirect/?next=/configuration/options/) and similar concerns. You can also rotate (and revoke) DSNs by navigating to _Settings > Projects > Client Keys (DSN)_.
+
+If your application is shipped to client devices, if possible, we recommend having a way to configure the DSN dynamically. In an ideal scenario, you can "ship" a new DSN to your application without the customer downloading the latest version. We recognize that this may not always be practical, but we cannot offer further advice as this scenario is implementation specific.
+
 ### Where to Find Your DSN
 
 If you forget your DSN, view _Settings -> Projects -> Client Keys (DSN)_ in [sentry.io](https://sentry.io/).

src/platforms/common/configuration/options.mdx

@@ -22,6 +22,8 @@ The _DSN_ tells the SDK where to send the events. If this value is not provided,
 
 In runtimes without a process environment (such as the browser) that fallback does not apply.
 
+Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-utilization).
+
 </ConfigKey>
 
 <ConfigKey name="stack-trace-mode" supported={["dotnet"]}>