opsentry 1.8.4__tar.gz

opsentry-1.8.4/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 OpSight Intelligence
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

opsentry-1.8.4/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: opsentry
+Version: 1.8.4
+Summary: AI agent security guardrails for engineering teams
+Author-email: OpSight Intelligence <utku@opsightintel.com>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/opsight-intelligence/opsentry
+Project-URL: Documentation, https://github.com/opsight-intelligence/opsentry#readme
+Project-URL: Repository, https://github.com/opsight-intelligence/opsentry
+Project-URL: Issues, https://github.com/opsight-intelligence/opsentry/issues
+Keywords: security,guardrails,claude-code,ai-agent,devsecops
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: Jinja2>=3.1
+Dynamic: license-file
+
+# OpSight OpSentry
+
+Three layers of defense for AI coding agents — **detect**, **prevent**, and **make dangerous actions architecturally impossible**.
+
+Competitors match patterns and lose the arms race. OpSentry makes entire attack classes impossible.
+
+Built by [OpSight Intelligence](https://github.com/opsight-intelligence).
+
+## Quick Start
+
+```bash
+# pip (recommended)
+pip install opsentry && opsentry install
+
+# Homebrew
+brew tap opsight-intelligence/opsentry && brew install opsentry && opsentry install
+
+# Git clone
+git clone https://github.com/opsight-intelligence/opsentry.git && cd opsentry && ./install.sh
+
+# GitHub Action (CI/CD)
+# uses: opsight-intelligence/opsentry-action@v1
+```
+
+Restart Claude Code after installation.
+
+## New in v1.8
+
+- **168 tests** (101 functional + 67 adversarial red-team) — up from 155 in v1.7. [red team log](https://github.com/opsight-intelligence/opsentry/blob/main/docs/red-team-log.md)
+- **Precision path matching** — `block-scope-escape.sh` rewritten with word-boundary regex and `realpath` symlink resolution. Project-local `.claude/` directories, `~/Library/` on macOS, `/var/folders/` (macOS temp), and filenames like `foo.bashrc.bak` are no longer over-blocked. Attack 3 protection is preserved and now also catches symlink-based bypass attempts against `$HOME/.claude/`.
+- **Configuration baseline integrity** — `install.sh` writes a SHA-256 manifest of the guardrail-controlled subset of `CLAUDE.md` and `settings.json` to `~/.claude/.opsentry-baseline.json`, locked with filesystem immutability. `opsentry patrol` re-verifies on every run and flags drift as a FAIL finding. User customizations (custom deny rules, custom hook matchers) are preserved — only the guardrail subset is hashed.
+- **Block log pattern analysis** — `opsentry patrol` now scans `~/.claude/guardrail-blocks.log` for five attack signatures beyond simple counts: repeat offender (same hook 5+/1h), rapid burst (5+ blocks in any 30s window), multi-hook coverage (3+ distinct hooks in 1h), exfiltration cluster (`block-sensitive-files` + `block-data-exfiltration` within 5 minutes), and self-modification attempts (Attack 3 active exploitation signal).
+- **Patrol bug fixes** — no longer aborts mid-execution when drift is detected (fixed `set -euo pipefail` interaction with `verify.sh` failures); no longer crashes on macOS due to the GNU-only `grep -oP` flag in the block log section.
+
+## v1.7 highlights (still current)
+
+- **Protection levels** — `strict` / `balanced` / `permissive` in `guardrails.yaml`
+- **Filesystem immutability** — `chflags uchg` (macOS) / `chattr +i` (Linux) locks guardrail files
+- **Compliance Patrol** — `opsentry patrol` with schedulable daily audits
+- **pip install** — `pip install opsentry` ships the CLI, deployment scripts, and config generator
+- **Red-team hardening** — all 8 hooks hardened against adversarial bypass vectors (67 red-team test cases)
+
+Full release history: [CHANGELOG.md](./CHANGELOG.md)
+
+## What Gets Installed
+
+| File | Location | Purpose |
+|------|----------|---------|
+| `CLAUDE.md` | `~/.claude/CLAUDE.md` | Behavioral rules Claude Code follows every session |
+| `settings.json` | `~/.claude/settings.json` | Hard deny rules for sensitive file access and dangerous commands |
+| `block-sensitive-files.sh` | `~/.claude/hooks/` | Blocks reading .env, credentials, secrets, certificates |
+| `block-dangerous-commands.sh` | `~/.claude/hooks/` | Blocks rm -rf, sudo, chmod 777, DROP TABLE, etc. |
+| `block-git-commands.sh` | `~/.claude/hooks/` | Blocks all git command execution |
+| `block-data-exfiltration.sh` | `~/.claude/hooks/` | Blocks curl/wget uploads, base64 of secrets, /tmp writes, netcat |
+| `block-package-install.sh` | `~/.claude/hooks/` | Blocks pip/npm/gem installs from untrusted sources |
+| `block-scope-escape.sh` | `~/.claude/hooks/` | Blocks self-modification of ~/.claude/ and system paths |
+| `block-environment-escape.sh` | `~/.claude/hooks/` | Blocks ssh, docker run/exec, terraform apply/destroy, kubectl |
+| `block-pii-leakage.sh` | `~/.claude/hooks/` | Blocks writing SSNs, credit card numbers, Korean RRNs into code |
+
+## How OpSentry Defends Your Environment
+
+### Layer 1 — Runtime Guardrails (Detect)
+
+Pre-execution pattern matching blocks known attack vectors before they run. 8 hook scripts, 203 tests, battle-tested against 8 red team attacks.
+
+- **CLAUDE.md** — behavioral rules Claude reads at session start (18 mandatory security sections)
+- **settings.json** — hard deny rules in Claude Code's permission system
+- **Hook scripts** — deterministic bash enforcement that inspects every tool call
+
+### Layer 2 — CI/CD Analysis (Prevent)
+
+Cross-file AST composition analysis catches exfiltration patterns that span multiple files at PR time. Import-graph-aware — detects when file-read, network-send, and sensitive-path references are assembled across imports.
+
+- **SEC-012** — cross-file exfiltration composition analysis (42 tests)
+- **SEC-013** — network exposure scanning (23 dangerous ports)
+- **Auto-fix** — `eval()` → `ast.literal_eval()`, bare `except:` → specific exceptions
+- **Merge gating** — critical/high findings block PR merge
+
+### Layer 3 — Sandbox Profiles (Make Impossible)
+
+Generated platform-specific sandbox configs that make dangerous actions impossible at the OS level. Not pattern matching — capability removal.
+
+- **macOS** — `sandbox-exec` SBPL profiles that deny read/write at the kernel level
+- **Linux** — bubblewrap wrapper scripts that shadow sensitive directories with empty mounts
+- **Docker** — Dockerfile + Compose with `cap_drop: ALL`, read-only root, network isolation
+
+```bash
+# Generate sandbox profiles from your guardrails.yaml
+opsentry sandbox generate --platform all --output-dir ./sandbox-profiles/
+```
+
+| Attack Class | How the Sandbox Defeats It |
+|---|---|
+| Credential file read (`.env`, `~/.aws/`) | Denied at kernel level, regardless of command syntax |
+| Guardrail self-destruction (`~/.claude/`) | Outside the sandbox namespace — invisible |
+| Data exfiltration via network | Network denied by default or allowlisted |
+| Persistence (cron, launchd, systemd) | Write access to persistence dirs denied |
+| Fork bombs / resource exhaustion | Process and memory limits enforced |
+
+You own the sandbox runtime — OpSentry provides the security intelligence. No vendor lock-in.
+
+## Updating
+
+When rules are updated in this repo, every developer should pull and re-run:
+
+```bash
+cd ai-guardrails
+./update.sh
+```
+
+## Verifying Installation
+
+To check that all guardrails are properly installed and unmodified:
+
+```bash
+./verify.sh
+```
+
+## Prerequisites
+
+- **jq** is required by the hook scripts. Install with:
+  - macOS: `brew install jq`
+  - Ubuntu/Debian: `sudo apt install jq`
+  - Windows (WSL): `sudo apt install jq`
+
+## What Is Blocked
+
+### Sensitive Files
+All `.env` files, credential configs, SSL certificates, SSH keys, cloud provider configs, database connection files, and anything in `secrets/`, `credentials/`, `private/`, or `keys/` directories.
+
+### Dangerous Commands
+`rm -rf`, `sudo`, `chmod 777`, `kill -9`, disk operations (`mkfs`, `dd`, `fdisk`), pipe-to-shell (`curl | bash`), and database destruction commands (`DROP TABLE`, `TRUNCATE`, `DELETE` without WHERE).
+
+### Git Commands
+All git commands are blocked from agent execution. The agent will write git commands as text for the developer to review and run manually.
+
+### Data Exfiltration
+Curl/wget file uploads, base64 encoding of sensitive files, writes to /tmp or /dev/shm, clipboard exfiltration of secrets, and netcat outbound channels.
+
+### Package Installs from Untrusted Sources
+pip/npm/gem/go installs from git URLs, custom registries, or direct download links. Standard registry installs are allowed.
+
+### Scope and Environment Escape
+Self-modification of `~/.claude/`, writes to system paths (`/etc`, `/usr`, shell configs), ssh/scp to remote hosts, docker run/exec/build, destructive terraform/kubectl commands.
+
+### PII in Source Code
+US Social Security Numbers, credit card numbers (Visa, Mastercard, Amex, Discover), and Korean Resident Registration Numbers are blocked from being written into code. Synthetic test values (000-00-0000, 555-55-5555) are allowed.
+
+### Client Data
+The CLAUDE.md includes strict rules against including client confidential data (company names, internal identifiers, business metrics) in any outputs.
+
+## Customisation
+
+- To add new file patterns to block, edit `claude/hooks/block-sensitive-files.sh` and `claude/settings.json`
+- To add new dangerous commands, edit `claude/hooks/block-dangerous-commands.sh`
+- To add new PII patterns, edit `claude/hooks/block-pii-leakage.sh`
+- To add new exfiltration vectors, edit `claude/hooks/block-data-exfiltration.sh`
+- To change behavioral rules, edit `claude/CLAUDE.md`
+- After changes, run `./ai-guardrails/test.sh` to validate, then `./ai-guardrails/install.sh` to deploy locally
+
+## Troubleshooting
+
+**Hooks not firing?**
+Run `/hooks` inside Claude Code to check if hooks are registered. Verify scripts are executable: `ls -la ~/.claude/hooks/`
+
+**"jq: command not found" errors?**
+Install jq — see Prerequisites above.
+
+**Developer modified their settings.json?**
+Run `./verify.sh` to check for differences. Run `./install.sh` to reset.
+
+## Questions or Issues
+
+Open an issue on [GitHub](https://github.com/opsight-intelligence/opsentry/issues) or reach out to the OpSight team.
+
+## Branch guard (pre-push hook)
+
+This repo's `main`/`develop` are protected by a client-side `pre-push` hook (the org is on GitHub Free, which has no server-side branch protection on private repos). The hook lives in `.git/hooks/`, so it is **not** version-controlled — **re-run the installer in every fresh clone**, from your `opsight-company` checkout:
+
+```sh
+bash scripts/git-hooks/install-hooks.sh /path/to/this-repo
+```
+
+It only guards `opsight-intelligence` remotes. For an intentional release push, override with `OPSIGHT_ALLOW_PROTECTED_PUSH=1 git push ...`. All changes go through a `feature/`/`bugfix/` branch → PR into `develop`.

opsentry-1.8.4/README.md

@@ -0,0 +1,184 @@
+# OpSight OpSentry
+
+Three layers of defense for AI coding agents — **detect**, **prevent**, and **make dangerous actions architecturally impossible**.
+
+Competitors match patterns and lose the arms race. OpSentry makes entire attack classes impossible.
+
+Built by [OpSight Intelligence](https://github.com/opsight-intelligence).
+
+## Quick Start
+
+```bash
+# pip (recommended)
+pip install opsentry && opsentry install
+
+# Homebrew
+brew tap opsight-intelligence/opsentry && brew install opsentry && opsentry install
+
+# Git clone
+git clone https://github.com/opsight-intelligence/opsentry.git && cd opsentry && ./install.sh
+
+# GitHub Action (CI/CD)
+# uses: opsight-intelligence/opsentry-action@v1
+```
+
+Restart Claude Code after installation.
+
+## New in v1.8
+
+- **168 tests** (101 functional + 67 adversarial red-team) — up from 155 in v1.7. [red team log](https://github.com/opsight-intelligence/opsentry/blob/main/docs/red-team-log.md)
+- **Precision path matching** — `block-scope-escape.sh` rewritten with word-boundary regex and `realpath` symlink resolution. Project-local `.claude/` directories, `~/Library/` on macOS, `/var/folders/` (macOS temp), and filenames like `foo.bashrc.bak` are no longer over-blocked. Attack 3 protection is preserved and now also catches symlink-based bypass attempts against `$HOME/.claude/`.
+- **Configuration baseline integrity** — `install.sh` writes a SHA-256 manifest of the guardrail-controlled subset of `CLAUDE.md` and `settings.json` to `~/.claude/.opsentry-baseline.json`, locked with filesystem immutability. `opsentry patrol` re-verifies on every run and flags drift as a FAIL finding. User customizations (custom deny rules, custom hook matchers) are preserved — only the guardrail subset is hashed.
+- **Block log pattern analysis** — `opsentry patrol` now scans `~/.claude/guardrail-blocks.log` for five attack signatures beyond simple counts: repeat offender (same hook 5+/1h), rapid burst (5+ blocks in any 30s window), multi-hook coverage (3+ distinct hooks in 1h), exfiltration cluster (`block-sensitive-files` + `block-data-exfiltration` within 5 minutes), and self-modification attempts (Attack 3 active exploitation signal).
+- **Patrol bug fixes** — no longer aborts mid-execution when drift is detected (fixed `set -euo pipefail` interaction with `verify.sh` failures); no longer crashes on macOS due to the GNU-only `grep -oP` flag in the block log section.
+
+## v1.7 highlights (still current)
+
+- **Protection levels** — `strict` / `balanced` / `permissive` in `guardrails.yaml`
+- **Filesystem immutability** — `chflags uchg` (macOS) / `chattr +i` (Linux) locks guardrail files
+- **Compliance Patrol** — `opsentry patrol` with schedulable daily audits
+- **pip install** — `pip install opsentry` ships the CLI, deployment scripts, and config generator
+- **Red-team hardening** — all 8 hooks hardened against adversarial bypass vectors (67 red-team test cases)
+
+Full release history: [CHANGELOG.md](./CHANGELOG.md)
+
+## What Gets Installed
+
+| File | Location | Purpose |
+|------|----------|---------|
+| `CLAUDE.md` | `~/.claude/CLAUDE.md` | Behavioral rules Claude Code follows every session |
+| `settings.json` | `~/.claude/settings.json` | Hard deny rules for sensitive file access and dangerous commands |
+| `block-sensitive-files.sh` | `~/.claude/hooks/` | Blocks reading .env, credentials, secrets, certificates |
+| `block-dangerous-commands.sh` | `~/.claude/hooks/` | Blocks rm -rf, sudo, chmod 777, DROP TABLE, etc. |
+| `block-git-commands.sh` | `~/.claude/hooks/` | Blocks all git command execution |
+| `block-data-exfiltration.sh` | `~/.claude/hooks/` | Blocks curl/wget uploads, base64 of secrets, /tmp writes, netcat |
+| `block-package-install.sh` | `~/.claude/hooks/` | Blocks pip/npm/gem installs from untrusted sources |
+| `block-scope-escape.sh` | `~/.claude/hooks/` | Blocks self-modification of ~/.claude/ and system paths |
+| `block-environment-escape.sh` | `~/.claude/hooks/` | Blocks ssh, docker run/exec, terraform apply/destroy, kubectl |
+| `block-pii-leakage.sh` | `~/.claude/hooks/` | Blocks writing SSNs, credit card numbers, Korean RRNs into code |
+
+## How OpSentry Defends Your Environment
+
+### Layer 1 — Runtime Guardrails (Detect)
+
+Pre-execution pattern matching blocks known attack vectors before they run. 8 hook scripts, 203 tests, battle-tested against 8 red team attacks.
+
+- **CLAUDE.md** — behavioral rules Claude reads at session start (18 mandatory security sections)
+- **settings.json** — hard deny rules in Claude Code's permission system
+- **Hook scripts** — deterministic bash enforcement that inspects every tool call
+
+### Layer 2 — CI/CD Analysis (Prevent)
+
+Cross-file AST composition analysis catches exfiltration patterns that span multiple files at PR time. Import-graph-aware — detects when file-read, network-send, and sensitive-path references are assembled across imports.
+
+- **SEC-012** — cross-file exfiltration composition analysis (42 tests)
+- **SEC-013** — network exposure scanning (23 dangerous ports)
+- **Auto-fix** — `eval()` → `ast.literal_eval()`, bare `except:` → specific exceptions
+- **Merge gating** — critical/high findings block PR merge
+
+### Layer 3 — Sandbox Profiles (Make Impossible)
+
+Generated platform-specific sandbox configs that make dangerous actions impossible at the OS level. Not pattern matching — capability removal.
+
+- **macOS** — `sandbox-exec` SBPL profiles that deny read/write at the kernel level
+- **Linux** — bubblewrap wrapper scripts that shadow sensitive directories with empty mounts
+- **Docker** — Dockerfile + Compose with `cap_drop: ALL`, read-only root, network isolation
+
+```bash
+# Generate sandbox profiles from your guardrails.yaml
+opsentry sandbox generate --platform all --output-dir ./sandbox-profiles/
+```
+
+| Attack Class | How the Sandbox Defeats It |
+|---|---|
+| Credential file read (`.env`, `~/.aws/`) | Denied at kernel level, regardless of command syntax |
+| Guardrail self-destruction (`~/.claude/`) | Outside the sandbox namespace — invisible |
+| Data exfiltration via network | Network denied by default or allowlisted |
+| Persistence (cron, launchd, systemd) | Write access to persistence dirs denied |
+| Fork bombs / resource exhaustion | Process and memory limits enforced |
+
+You own the sandbox runtime — OpSentry provides the security intelligence. No vendor lock-in.
+
+## Updating
+
+When rules are updated in this repo, every developer should pull and re-run:
+
+```bash
+cd ai-guardrails
+./update.sh
+```
+
+## Verifying Installation
+
+To check that all guardrails are properly installed and unmodified:
+
+```bash
+./verify.sh
+```
+
+## Prerequisites
+
+- **jq** is required by the hook scripts. Install with:
+  - macOS: `brew install jq`
+  - Ubuntu/Debian: `sudo apt install jq`
+  - Windows (WSL): `sudo apt install jq`
+
+## What Is Blocked
+
+### Sensitive Files
+All `.env` files, credential configs, SSL certificates, SSH keys, cloud provider configs, database connection files, and anything in `secrets/`, `credentials/`, `private/`, or `keys/` directories.
+
+### Dangerous Commands
+`rm -rf`, `sudo`, `chmod 777`, `kill -9`, disk operations (`mkfs`, `dd`, `fdisk`), pipe-to-shell (`curl | bash`), and database destruction commands (`DROP TABLE`, `TRUNCATE`, `DELETE` without WHERE).
+
+### Git Commands
+All git commands are blocked from agent execution. The agent will write git commands as text for the developer to review and run manually.
+
+### Data Exfiltration
+Curl/wget file uploads, base64 encoding of sensitive files, writes to /tmp or /dev/shm, clipboard exfiltration of secrets, and netcat outbound channels.
+
+### Package Installs from Untrusted Sources
+pip/npm/gem/go installs from git URLs, custom registries, or direct download links. Standard registry installs are allowed.
+
+### Scope and Environment Escape
+Self-modification of `~/.claude/`, writes to system paths (`/etc`, `/usr`, shell configs), ssh/scp to remote hosts, docker run/exec/build, destructive terraform/kubectl commands.
+
+### PII in Source Code
+US Social Security Numbers, credit card numbers (Visa, Mastercard, Amex, Discover), and Korean Resident Registration Numbers are blocked from being written into code. Synthetic test values (000-00-0000, 555-55-5555) are allowed.
+
+### Client Data
+The CLAUDE.md includes strict rules against including client confidential data (company names, internal identifiers, business metrics) in any outputs.
+
+## Customisation
+
+- To add new file patterns to block, edit `claude/hooks/block-sensitive-files.sh` and `claude/settings.json`
+- To add new dangerous commands, edit `claude/hooks/block-dangerous-commands.sh`
+- To add new PII patterns, edit `claude/hooks/block-pii-leakage.sh`
+- To add new exfiltration vectors, edit `claude/hooks/block-data-exfiltration.sh`
+- To change behavioral rules, edit `claude/CLAUDE.md`
+- After changes, run `./ai-guardrails/test.sh` to validate, then `./ai-guardrails/install.sh` to deploy locally
+
+## Troubleshooting
+
+**Hooks not firing?**
+Run `/hooks` inside Claude Code to check if hooks are registered. Verify scripts are executable: `ls -la ~/.claude/hooks/`
+
+**"jq: command not found" errors?**
+Install jq — see Prerequisites above.
+
+**Developer modified their settings.json?**
+Run `./verify.sh` to check for differences. Run `./install.sh` to reset.
+
+## Questions or Issues
+
+Open an issue on [GitHub](https://github.com/opsight-intelligence/opsentry/issues) or reach out to the OpSight team.
+
+## Branch guard (pre-push hook)
+
+This repo's `main`/`develop` are protected by a client-side `pre-push` hook (the org is on GitHub Free, which has no server-side branch protection on private repos). The hook lives in `.git/hooks/`, so it is **not** version-controlled — **re-run the installer in every fresh clone**, from your `opsight-company` checkout:
+
+```sh
+bash scripts/git-hooks/install-hooks.sh /path/to/this-repo
+```
+
+It only guards `opsight-intelligence` remotes. For an intentional release push, override with `OPSIGHT_ALLOW_PROTECTED_PUSH=1 git push ...`. All changes go through a `feature/`/`bugfix/` branch → PR into `develop`.