Browser tab content: # Secure OpenReplay It’s highly recommended to only allow open…
- User
Browser tab content: # Secure OpenReplay
It’s highly recommended to only allow open ports 80/443 to the machine using security groups. There are some componenes litening to the 0.0.0.0 address, to make networking easier, like k3s server api, flannel api etc.
If you’re bringing your own certificate, create an SSL secret using the following command:
kubectl create secret tls openreplay-ssl -n app --key="private_key_file.pem" --cert="certificate.crt".Note: If you don’t have a certificate, generate one, that auto-renews, for your subdomain (the one provided during installation) using Let’s Encrypt. Simply connect to OpenReplay instance, run
cd openreplay/scripts/helmcharts && bash certmanager.shand follow the steps.If you wish to enable http to https redirection (recommended) edit the configuration using
openreplay -e, then uncomment the below block, under theingress-nginxsection:ingress-nginx: &ingress-nginx controller: config: ssl-redirect: true force-ssl-redirect: trueNote: Our
ingress-nginxruns by default on ports80|443, but this can be easily changed, if needed, invars.yaml:ingress-nginx: &ingress-nginx controller: service: ports: http: 80 https: 443Save and exit using
:wqfor the service to reload.To indicate whether or not a browser should be allowed to render a page in a
<frame>, <iframe>, <embed>or<object>and avoid click-jacking attacks, set theX-Frame-Optionsresponse header by editing the configuration usingopenreplay -e:ingress-nginx: &ingress-nginx controller: addHeaders: X-Frame-Options: "SAMEORIGIN"Then, save and exit using
:wqfor the service to reload.OpenReplay supports reCaptcha (v2) for additional security. To enable this protection:
- Get a v2 reCaptcha key from Google, with
invisiblemode enabled, i.e. do not prompt fortick I am not a human. - Open
/var/lib/openreplay/vars.yamlthen uncomment and update the below env variables inchalicesection:
captcha_server: The URL to your reCaptcha service (e.g. https://www.google.com/recaptcha/api/siteverify)captcha_key: You reCaptcha secret key
- Edit
.envinopenreplay/frontend/(copy.env.sampleif it does not exist) and substitute theCAPTCHA_SITE_KEYvariable with your reCaptcha site key. - Rebuild the frontend:
cd openreplay/frontend IMAGE_TAG=my-custom-image PUSH_IMAGE=1 DOCKER_REPO=my-docker-user-name bash -x build.sh- Open
/var/lib/openreplay/vars.yamland specify your newly built frontend image in thefrontendblock:
frontend: image: repository: "my-docker-username/frontend" tag: "my-custom-image"- Restart the frontend and web server services for the changes to take effect:
openreplay -RHere is an example of a policy (CSP) for allowing OpenReplay to record sessions. This has to be adapted depending on your domain and security requirements:
worker-src ‘self’ blob: https://openreplay.mycompany.com https://*.openreplay.com; script-src ‘self’ https://openreplay.mycompany.com https://*.openreplay.com;To apply your CSP to NGINX, connect to your OpenReplay instance and follow the below steps:
- Run
openreplay -eand add your CSP in thefrontendblock. Make sure to update
frontend: ingress: cspSnippet: | add_header Content-Security-Policy "worker-src 'self' blob: https://openreplay.mycompany.com https://*.openreplay.com; script-src 'self' https://openreplay.mycompany.com https://*.openreplay.com;";Note: Make sure to replace
https://openreplay.mycompany.comoccurences in the above CSP with your OpenReplay domain name. The value should be the same asDOMAIN_NAMEin/var/lib/openreplay/vars.yamlfile.- Save and exit using
:wqto apply your newly added CSP
Cross-domain requests are allowed, by default, from all origins (
Access-Control-Allow-Origin: *). If you wish to restrict recordings from few domains only, then runopenreplay -eand update thehttpblock by adding the below annotations:http: ingress: annotations: nginx.ingress.kubernetes.io/cors-allow-methods: POST nginx.ingress.kubernetes.io/cors-allow-headers: Content-Type,Authorization,Content-Encoding nginx.ingress.kubernetes.io/cors-allow-origin: https://app1.mycompany.com,https://app2.mycompany.com,https://*.mycompany.com nginx.ingress.kubernetes.io/enable-cors: "true" nginx.ingress.kubernetes.io/cors-expose-headers: "Content-Length"Then save and exit using
:wqto apply your newly added CSP.If you have any questions about this process, feel free to reach out to us on our Slack or check out our Forum.
Was siehst du?
- Get a v2 reCaptcha key from Google, with
- Assistant
Der Inhalt des Browser-Tabs zeigt eine Anleitung zur Absicherung von OpenReplay, einer Open-Source-Plattform zur Sitzungsaufzeichnung. Die Anleitung umfasst mehrere sicherheitsbezogene Konfigurationen:
-
Offene Ports beschränken: Es wird empfohlen, nur die Ports 80 und 443 über Sicherheitsgruppen zuzulassen.
-
SSL-Zertifikate: Anleitung zur Erstellung eines SSL-Secrets mit
kubectl, falls man ein eigenes Zertifikat mitbringt, oder zur Verwendung von Let's Encrypt für ein automatisch erneuerndes Zertifikat. -
HTTP zu HTTPS-Umleitung: Beschreibung, wie man die Umleitung von HTTP zu HTTPS konfiguriert, indem man eine bestimmte Blockkonfiguration in
ingress-nginxbearbeitet. -
X-Frame-Options Header: Anweisungen zum Setzen des Headers
X-Frame-Options: "SAMEORIGIN"zur Vermeidung von Clickjacking-Angriffen. -
reCaptcha Integration: Schritte zur Aktivierung von reCaptcha v2, um zusätzliche Sicherheit durch Mensch-Maschine-Unterscheidung zu implementieren.
-
Content-Security-Policy (CSP): Beispiel einer CSP zur Anpassung an die eigenen Sicherheitsanforderungen, zusammen mit Hinweisen zur Konfiguration über NGINX.
-
CORS-Beschränkungen: Anleitung, wie man Cross-Origin Resource Sharing (CORS) einschränken und nur bestimmte Domains zulassen kann.
Zusätzlich wird auf Kommunikationskanäle wie den Slack-Kanal und das Forum von OpenReplay verwiesen, die für Fragen zur Verfügung stehen.
-