> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/security-and-safety/voices-of-vr-786-xr-safety-initiative-security-privacy-and-ethics-in-xr.md).

# Voices Of VR #786: XR Safety Initiative: Security, Privacy, & Ethics in XR

The XR Safety Initiative (XRSI), co-founded by Kavya Pearlman, was announced at the Open AR Cloud Symposium on May 28, 2019.

## Overview

**Authors:** Voices of VR with Kent Bye

**Publication Date:** 26 July 2019

**Link:** <https://voicesofvr.com/786-xr-safety-initiative-security-privacy-ethics-in-xr>

**Keywords:** XR safety, VR security, XR security risks, immersive tech threats, VR attacks, XRSI, human joystick attack, chaperone system exploits, cybersecurity in XR, AR/VR privacy, haptic exploits, XR ethics

**Type:** Audio/Podcast

## Summary

The XR Safety Initiative (XRSI), co-founded by Kavya Pearlman, was announced at the Open AR Cloud Symposium on May 28, 2019. XRSI collaborates with security researcher Ibrahim Baggili, whose 2019 IEEE paper detailed VR attacks that manipulate users' movements by altering virtual environments. Baggili, alongside Casey and Yarramreddy, demonstrated exploits disabling chaperone systems to direct users physically. Pearlman partnered with Baggili and Regine Bonneu to establish XRSI, which now categorizes security threats and seeks collaboration with developers and major companies to establish safety best practices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.xrguild.org/security-and-safety/voices-of-vr-786-xr-safety-initiative-security-privacy-and-ethics-in-xr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
