# Safety and Security

Omega OS applies defense-in-depth security.

## Sandboxing

* Node integration disabled
* Context isolation enforced
* Renderer sandbox enabled
* Restricted filesystem access

## Encryption

* Wallet keys encrypted at rest
* Secure local storage
* SHA-256 document hashing

## Secure Communication

* Context bridge IPC only
* No direct system API access
* Explicit API exposure

## Security Best Practices

* Regular dependency audits
* Minimal attack surface
* Secure default configurations
* Isolated execution environment

{% hint style="info" %}
Omega OS provides Tor Browser-level security system-wide.
{% endhint %}

## Hardening & Security Enhancements

### Network Hardening

* **Mandatory Tor routing**
* Node.js requests routed via SOCKS5
* WebRTC disabled
* DNS leak prevention
* Background networking blocked
* Local services preserved

### Fingerprinting Protection

* Navigator API spoofing
* Canvas noise injection
* Audio fingerprint protection
* Font enumeration limits
* Standardized user agent

### Chromium Hardening

* Remote fonts blocked
* Canvas extraction blocked
* Spellcheck disabled
* Safe browsing disabled
* Insecure protocols blocked
* File access restricted

{% hint style="success" %}
Key Advantages

* Complete environment isolation
* No external Tor installation
* Application-level routing
* Enhanced fingerprint protection
* Local services remain functional
* Integrated privacy at every layer
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://omega-6.gitbook.io/omega/omega-os/safety-and-security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.