<commit_before># Security Notice

The SkyWalking OAP server and UI should run in a secure environment, such as only inside your data center.
OAP server, UI, and all agents deployment should only be reachable by the operation team only on default
deployment.

All telemetry data are trusted. The OAP server **would not validate any field** of the telemetry data to avoid extra
load for the server.

It is up to the operator(OPS team) whether to expose the OAP server, UI, or some agent deployment to unsecured
environment.
The following security policies should be considered to add to secure your SkyWalking deployment.

1. HTTPs and gRPC+TLS should be used between agents and OAP servers, as well as UI.
2. Set up TOKEN or username/password based authentications for the OAP server and UI through your Gateway.
3. Validate all fields in the body of the traceable RPC(including HTTP 1/2, MQ) headers when requests are from out of
   the trusted zone.
4. All fields of telemetry data(HTTP in raw text or encoded Protobuf format) should be validated and reject malicious
   data.

Without these protections, an attacker could embed executable Javascript code in those fields, causing XSS or even
Remote Code Execution (RCE) issues.

For some sensitive environment, consider to limit the telemetry report frequency in case of DoS/DDoS for exposed OAP
and UI services.

## appendix

The SkyWalking [client-js](https://github.com/apache/skywalking-client-js) agent is always running out of the secured
environment. Please follow its **security notice** for more details.<commit_msg>Add more details on security notice (#9778)<commit_after># Security Notice

The SkyWalking OAP server, UI, and agent deployments should run in a secure environment, such as only inside your data center.
OAP server, UI, and agent deployments should only be reachable by the operation team on default
deployment.

All telemetry data are trusted. The OAP server **would not validate any field** of the telemetry data to avoid extra
load for the server.

It is up to the operator(OPS team) whether to expose the OAP server, UI, or some agent deployment to unsecured
environment.
The following security policies should be considered to add to secure your SkyWalking deployment.

1. HTTPs and gRPC+TLS should be used between agents and OAP servers, as well as UI.
2. Set up TOKEN or username/password based authentications for the OAP server and UI through your Gateway.
3. Validate all fields of the traceable RPC(including HTTP 1/2, MQ) headers(header names are `sw8`, `sw8-x` and `sw8-correlation`) 
   when requests are from out of the trusted zone. Or simply block/remove those headers unless you are using the client-js agent.
4. All fields of telemetry data(HTTP in raw text or encoded Protobuf format) should be validated and reject malicious
   data.

Without these protections, an attacker could embed executable Javascript code in those fields, causing XSS or even
Remote Code Execution (RCE) issues.

For some sensitive environment, consider to limit the telemetry report frequency in case of DoS/DDoS for exposed OAP
and UI services.

## appendix

The SkyWalking [client-js](https://github.com/apache/skywalking-client-js) agent is always running out of the secured
environment. Please follow its **security notice** for more details.

{'fraction_non_alphanumeric': 0.04609822235613136, 'fraction_numerical': 0.005724615848147032, 'mean_word_length': 4.561139028475712, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6687900', 'n_tokens_mistral': 858, 'n_tokens_neox': 823, 'n_words': 502}