resksecure 0.1.0__tar.gz

resksecure-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,51 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      publish_to_pypi:
+        description: "Publish to PyPI (true) or TestPyPI (false)"
+        required: true
+        default: "true"
+
+jobs:
+  build-and-publish:
+    name: Build and publish Python package
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade pip
+          pip install hatchling
+
+      - name: Build package
+        run: python -m hatchling build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        if: ${{ github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && inputs.publish_to_pypi == 'true') }}
+        with:
+          packages-dir: dist/
+          password: ${{ secrets.PYPI_TOKEN }}
+
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.publish_to_pypi != 'true' }}
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          packages-dir: dist/
+          password: ${{ secrets.PYPI_TOKEN }}

resksecure-0.1.0/.github/workflows/tests.yml

@@ -0,0 +1,38 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    name: Run tests
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.13", "3.14"]
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e .[dev]
+
+      - name: Lint with ruff
+        run: ruff check src/ tests/
+
+      - name: Run tests
+        run: python -m pytest tests/ -v
+
+      - name: Test import
+        run: python -c "from resksecure import BitmaskLogitsProcessor, load_policy, verify_tool_action; print('All imports OK')"

resksecure-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.pyc
+*.pyo
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+*.egg
+.DS_Store
+.env

resksecure-0.1.0/LICENSE

@@ -0,0 +1,105 @@
+RESK SOFTWARE LICENSE
+Version 1.0, June 2026
+
+Copyright (c) 2026 RESK Security
+
+TERMS AND CONDITIONS
+
+1. Definitions
+
+"Software" means the source code, documentation, and any accompanying
+materials in this repository.
+
+"Licensor" means RESK Security.
+
+"Licensee" means any individual or entity that accesses or uses the Software.
+
+"Commercial Use" means any use of the Software where the primary purpose
+is commercial advantage or monetary compensation, including but not limited
+to: integrating the Software into a commercial product, offering the Software
+as part of a SaaS service, using the Software for internal business operations
+that generate revenue, or distributing the Software in exchange for any form
+of payment.
+
+"Royalty" means the recurring fee payable to Licensor for any Commercial Use
+of the Software, as defined in a separate commercial agreement.
+
+2. Grant of License
+
+Subject to the terms and conditions of this License, Licensor grants Licensee
+a non-exclusive, non-transferable, non-sublicensable, limited license to:
+
+(a) View and study the Software source code.
+(b) Use the Software for non-commercial, personal, educational, or
+    evaluation purposes only.
+(c) Modify the Software for personal, non-commercial use only.
+
+3. Prohibited Uses
+
+Without the prior written consent of Licensor, Licensee may NOT:
+
+(a) Use the Software for any Commercial Use.
+(b) Distribute, sublicense, sell, lease, rent, or transfer the Software
+    or any derivative thereof to any third party.
+(c) Incorporate the Software or any portion thereof into any product or
+    service offered to third parties.
+(d) Remove or alter any copyright, trademark, or proprietary notice
+    contained in the Software.
+(e) Use the Software in any manner that competes with Licensor's business.
+(f) Create derivative works based on the Software for distribution or
+    Commercial Use.
+(g) Use the Software in any environment that processes sensitive personal
+    data without prior written authorization from Licensor.
+
+4. Commercial License and Royalties
+
+Any Commercial Use of the Software requires a separate commercial license
+agreement signed by both parties. Such agreement shall specify:
+
+(a) The scope of permitted Commercial Use.
+(b) Royalty fees, which shall be calculated as a percentage of revenue or
+    a fixed fee per deployment, as agreed upon in writing.
+(c) Duration and renewal terms.
+
+Contact: resk-security@proton.me for commercial licensing inquiries.
+
+5. Intellectual Property
+
+All right, title, and interest in and to the Software, including all
+intellectual property rights therein, remain the exclusive property of
+Licensor. This License does not transfer any ownership rights to Licensee.
+
+6. No Warranty
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL
+THE LICENSOR BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+7. Limitation of Liability
+
+In no event shall Licensor be liable for any indirect, incidental, special,
+consequential, or punitive damages, including but not limited to loss of
+profits, data, or use, arising out of or in connection with the Software,
+whether based on warranty, contract, tort, or any other legal theory, even
+if Licensor has been advised of the possibility of such damages.
+
+8. Termination
+
+This License terminates automatically if Licensee fails to comply with any
+of its terms. Upon termination, Licensee must immediately cease all use of
+the Software and destroy all copies. Licensor reserves the right to pursue
+legal remedies for any unauthorized use.
+
+9. Governing Law
+
+This License shall be governed by and construed in accordance with the laws
+of France, without regard to its conflict of laws principles.
+
+10. Entire Agreement
+
+This License constitutes the entire agreement between the parties concerning
+the subject matter hereof and supersedes all prior agreements and
+understandings.

resksecure-0.1.0/PKG-INFO

@@ -0,0 +1,238 @@
+Metadata-Version: 2.4
+Name: resksecure
+Version: 0.1.0
+Summary: Bitmask-based LLM security firewall with policy-driven logits filtering using GPU-accelerated Aho-Corasick pattern matching
+Project-URL: Homepage, https://github.com/Resk-Security/reskSecure
+Project-URL: Repository, https://github.com/Resk-Security/reskSecure
+Project-URL: Documentation, https://github.com/Resk-Security/reskSecure
+Author: RESK Security
+License: RESK Software License
+License-File: LICENSE
+Keywords: aho-corasick,bitmask,dlp,filtering,firewall,gpu,llm,logits,permissions,policy,safety,security,transformers
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: Other/Proprietary License
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.13
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: resklogits>=0.1.0
+Requires-Dist: torch>=2.0.0
+Requires-Dist: transformers>=4.35.0
+Provides-Extra: dev
+Requires-Dist: black>=23.0.0; extra == 'dev'
+Requires-Dist: mypy>=1.0.0; extra == 'dev'
+Requires-Dist: pytest>=7.0.0; extra == 'dev'
+Requires-Dist: ruff>=0.1.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# reskSecure
+
+[![PyPI version](https://img.shields.io/pypi/v/resksecure)](https://pypi.org/project/resksecure/)
+[![PyPI downloads](https://img.shields.io/pypi/dm/resksecure)](https://pypi.org/project/resksecure/)
+[![Python versions](https://img.shields.io/pypi/pyversions/resksecure)](https://pypi.org/project/resksecure/)
+[![License](https://img.shields.io/badge/license-RESK-blue)](LICENSE)
+
+**Bitmask-based LLM security firewall.** A Python package that restricts what a language model can generate based on user permissions encoded as a bitmask. It works by intercepting the model's token predictions and blocking or penalizing disallowed phrases before they appear in the output.
+
+Available on [PyPI](https://pypi.org/project/resksecure/).
+
+Unlike prompt-based filters (which can be jailbroken) or post-generation content moderation (which lets forbidden content leak before detection), reskSecure acts at the logits level -- directly inside the model's generation loop. Each token must pass through the security policy before being emitted.
+
+---
+
+## How it works
+
+```
+User request with bitmask (e.g. 7)
+    |
+    v
+BitmaskLogitsProcessor intercepts each token prediction
+    |
+    v
+For every candidate token, the Aho-Corasick automaton (from resklogits)
+checks if selecting it would start or complete a banned phrase
+    |
+    v
+Hard-mode phrases: the token's logit is set to -inf (impossible to generate)
+Bias-mode phrases: the token's logit is reduced by a configurable penalty
+    |
+    v
+On complete match: EOS token is forced, generation stops immediately
+    |
+    v
+Output response or tool call
+```
+
+Tool calls are also blocked at the token level. If the user's bitmask does not
+contain the required bit for a tool, that tool's trigger phrases (like
+`"send_email("` or `"create_ticket("`) are automatically added to the
+hard-mode blocked list. The model can never generate the first token of
+a disallowed tool call, regardless of prompt engineering or jailbreak
+attempts.
+
+A post-generation check (`verify_tool_action`) is also available as a
+defense-in-depth layer, but the primary protection is at the logits level.
+
+---
+
+## Why not just prompt engineering?
+
+- Prompt injections can bypass instruction-based filters
+- Post-generation regex or classifier scans catch violations after they appear, but the forbidden content has already been emitted
+- Logits-level filtering blocks tokens before they are sampled -- the model never "sees" the banned sequence as a completion candidate
+
+---
+
+## Features
+
+- **Two severity modes**: `hard` blocks tokens completely (-inf logit), `bias` reduces probability by a configurable penalty
+- **Strict mode**: forces end-of-sequence as soon as the generated prefix matches the start of a banned phrase, even before the full phrase is formed
+- **GPU-accelerated pattern matching**: uses VectorizedAhoCorasick from the resklogits package for fast token scanning
+- **Policy system**: YAML configuration associates capability bitmasks with phrase rules and tool permissions
+- **Hot-reload**: PolicyWatcher detects file changes and rebuilds the automaton without restarting the server
+- **Thread-safe cache**: automata are cached by (mask, model_name) with configurable TTL
+- **Tool guard**: post-generation bitmask check for tool call execution
+- **No JWT handling**: the package receives a raw integer bitmask; authentication and JWT decoding are handled by the calling application
+
+---
+
+## Requirements
+
+- Python >= 3.13
+- PyTorch >= 2.0.0
+- transformers >= 4.35.0
+- resklogits >= 0.1.0
+
+---
+
+## Installation
+
+```bash
+pip install resksecure
+```
+
+[![PyPI version](https://img.shields.io/pypi/v/resksecure)](https://pypi.org/project/resksecure/)
+[![PyPI downloads](https://img.shields.io/pypi/dm/resksecure)](https://pypi.org/project/resksecure/)
+
+From source:
+
+```bash
+git clone https://github.com/Resk-Security/reskSecure.git
+cd reskSecure
+pip install -e .
+```
+
+---
+
+## Quick start
+
+Define a policy file (`policy.yaml`):
+
+```yaml
+version: "1.0"
+policies:
+  - mask: 7
+    name: contributor
+    strict: false
+    default: true
+    rules:
+      - phrase: "DROP TABLE"
+        mode: hard
+      - phrase: "DELETE FROM"
+        mode: hard
+      - phrase: "salaries"
+        mode: bias
+        penalty: -5.0
+    tools:
+      read_email:
+        required_bit: 0
+      send_email:
+        required_bit: 1
+      read_sql:
+        required_bit: 2
+```
+
+Use it in your generation pipeline:
+
+```python
+from resksecure import BitmaskLogitsProcessor, load_policy, verify_tool_action
+
+policy_set = load_policy("policy.yaml")
+
+processor = BitmaskLogitsProcessor(
+    mask=7,
+    model_name="mistralai/Mistral-7B-v0.1",
+    tokenizer=tokenizer,
+    policy_set=policy_set,
+    device="cuda",
+)
+
+outputs = model.generate(**inputs, logits_processor=[processor])
+
+# Optional: verify tool calls against the bitmask
+if has_tool_call(response):
+    if not verify_tool_action("send_email", user_mask=7, policy_set=policy_set):
+        raise PermissionError("Action not authorized")
+```
+
+---
+
+## Policy reference
+
+Policy-level fields:
+
+| Field       | Type    | Description                                              |
+|-------------|---------|----------------------------------------------------------|
+| `mask`      | int     | Capability bitmask that identifies this policy           |
+| `name`      | string  | Human-readable policy name                               |
+| `strict`    | bool    | If true, stop generation at the first banned prefix      |
+| `default`   | bool    | If true, this policy is used when no exact mask matches  |
+| `rules`     | list    | List of phrase rules (see below)                         |
+| `tools`     | dict    | Map of tool names to tool rule objects (see below)       |
+
+Phrase rule fields:
+
+| Field     | Type   | Description                                                |
+|-----------|--------|------------------------------------------------------------|
+| `phrase`  | string | Text pattern to ban or penalize                            |
+| `mode`    | string | Either `hard` (block completely) or `bias` (reduce logits) |
+| `penalty` | float  | Logit penalty for bias mode (e.g. -5.0)                   |
+
+Tool rule fields:
+
+| Field              | Type     | Description                                                    |
+|--------------------|----------|----------------------------------------------------------------|
+| `required_bit`     | int      | Bit position that must be set in the user mask to use this tool |
+| `trigger_phrases`  | string[] | Phrases that start this tool call (blocked if bit not set)      |
+
+---
+
+## Package structure
+
+```
+reskSecure/
+  src/resksecure/
+    __init__.py              Public exports, version
+    policy_loader.py         YAML parsing, Policy/PolicySet models
+    trie_factory.py          Builds VectorizedAhoCorasick from a Policy
+    bitmask_processor.py     BitmaskLogitsProcessor (LogitsProcessor subclass)
+    tool_guard.py            Post-generation tool action verification
+    cache.py                 Thread-safe TTL cache for automata
+    policy_watcher.py        Hot-reload daemon that watches YAML mtime
+    config/example_policy.yaml
+  tests/
+  examples/
+```
+
+---
+
+## License
+
+This software is licensed under the RESK Software License. Commercial use requires a separate paid license. See the [LICENSE](LICENSE) file for details.
+
+For commercial licensing inquiries, contact: contact@resk.fr

resksecure-0.1.0/README.md

@@ -0,0 +1,206 @@
+# reskSecure
+
+[![PyPI version](https://img.shields.io/pypi/v/resksecure)](https://pypi.org/project/resksecure/)
+[![PyPI downloads](https://img.shields.io/pypi/dm/resksecure)](https://pypi.org/project/resksecure/)
+[![Python versions](https://img.shields.io/pypi/pyversions/resksecure)](https://pypi.org/project/resksecure/)
+[![License](https://img.shields.io/badge/license-RESK-blue)](LICENSE)
+
+**Bitmask-based LLM security firewall.** A Python package that restricts what a language model can generate based on user permissions encoded as a bitmask. It works by intercepting the model's token predictions and blocking or penalizing disallowed phrases before they appear in the output.
+
+Available on [PyPI](https://pypi.org/project/resksecure/).
+
+Unlike prompt-based filters (which can be jailbroken) or post-generation content moderation (which lets forbidden content leak before detection), reskSecure acts at the logits level -- directly inside the model's generation loop. Each token must pass through the security policy before being emitted.
+
+---
+
+## How it works
+
+```
+User request with bitmask (e.g. 7)
+    |
+    v
+BitmaskLogitsProcessor intercepts each token prediction
+    |
+    v
+For every candidate token, the Aho-Corasick automaton (from resklogits)
+checks if selecting it would start or complete a banned phrase
+    |
+    v
+Hard-mode phrases: the token's logit is set to -inf (impossible to generate)
+Bias-mode phrases: the token's logit is reduced by a configurable penalty
+    |
+    v
+On complete match: EOS token is forced, generation stops immediately
+    |
+    v
+Output response or tool call
+```
+
+Tool calls are also blocked at the token level. If the user's bitmask does not
+contain the required bit for a tool, that tool's trigger phrases (like
+`"send_email("` or `"create_ticket("`) are automatically added to the
+hard-mode blocked list. The model can never generate the first token of
+a disallowed tool call, regardless of prompt engineering or jailbreak
+attempts.
+
+A post-generation check (`verify_tool_action`) is also available as a
+defense-in-depth layer, but the primary protection is at the logits level.
+
+---
+
+## Why not just prompt engineering?
+
+- Prompt injections can bypass instruction-based filters
+- Post-generation regex or classifier scans catch violations after they appear, but the forbidden content has already been emitted
+- Logits-level filtering blocks tokens before they are sampled -- the model never "sees" the banned sequence as a completion candidate
+
+---
+
+## Features
+
+- **Two severity modes**: `hard` blocks tokens completely (-inf logit), `bias` reduces probability by a configurable penalty
+- **Strict mode**: forces end-of-sequence as soon as the generated prefix matches the start of a banned phrase, even before the full phrase is formed
+- **GPU-accelerated pattern matching**: uses VectorizedAhoCorasick from the resklogits package for fast token scanning
+- **Policy system**: YAML configuration associates capability bitmasks with phrase rules and tool permissions
+- **Hot-reload**: PolicyWatcher detects file changes and rebuilds the automaton without restarting the server
+- **Thread-safe cache**: automata are cached by (mask, model_name) with configurable TTL
+- **Tool guard**: post-generation bitmask check for tool call execution
+- **No JWT handling**: the package receives a raw integer bitmask; authentication and JWT decoding are handled by the calling application
+
+---
+
+## Requirements
+
+- Python >= 3.13
+- PyTorch >= 2.0.0
+- transformers >= 4.35.0
+- resklogits >= 0.1.0
+
+---
+
+## Installation
+
+```bash
+pip install resksecure
+```
+
+[![PyPI version](https://img.shields.io/pypi/v/resksecure)](https://pypi.org/project/resksecure/)
+[![PyPI downloads](https://img.shields.io/pypi/dm/resksecure)](https://pypi.org/project/resksecure/)
+
+From source:
+
+```bash
+git clone https://github.com/Resk-Security/reskSecure.git
+cd reskSecure
+pip install -e .
+```
+
+---
+
+## Quick start
+
+Define a policy file (`policy.yaml`):
+
+```yaml
+version: "1.0"
+policies:
+  - mask: 7
+    name: contributor
+    strict: false
+    default: true
+    rules:
+      - phrase: "DROP TABLE"
+        mode: hard
+      - phrase: "DELETE FROM"
+        mode: hard
+      - phrase: "salaries"
+        mode: bias
+        penalty: -5.0
+    tools:
+      read_email:
+        required_bit: 0
+      send_email:
+        required_bit: 1
+      read_sql:
+        required_bit: 2
+```
+
+Use it in your generation pipeline:
+
+```python
+from resksecure import BitmaskLogitsProcessor, load_policy, verify_tool_action
+
+policy_set = load_policy("policy.yaml")
+
+processor = BitmaskLogitsProcessor(
+    mask=7,
+    model_name="mistralai/Mistral-7B-v0.1",
+    tokenizer=tokenizer,
+    policy_set=policy_set,
+    device="cuda",
+)
+
+outputs = model.generate(**inputs, logits_processor=[processor])
+
+# Optional: verify tool calls against the bitmask
+if has_tool_call(response):
+    if not verify_tool_action("send_email", user_mask=7, policy_set=policy_set):
+        raise PermissionError("Action not authorized")
+```
+
+---
+
+## Policy reference
+
+Policy-level fields:
+
+| Field       | Type    | Description                                              |
+|-------------|---------|----------------------------------------------------------|
+| `mask`      | int     | Capability bitmask that identifies this policy           |
+| `name`      | string  | Human-readable policy name                               |
+| `strict`    | bool    | If true, stop generation at the first banned prefix      |
+| `default`   | bool    | If true, this policy is used when no exact mask matches  |
+| `rules`     | list    | List of phrase rules (see below)                         |
+| `tools`     | dict    | Map of tool names to tool rule objects (see below)       |
+
+Phrase rule fields:
+
+| Field     | Type   | Description                                                |
+|-----------|--------|------------------------------------------------------------|
+| `phrase`  | string | Text pattern to ban or penalize                            |
+| `mode`    | string | Either `hard` (block completely) or `bias` (reduce logits) |
+| `penalty` | float  | Logit penalty for bias mode (e.g. -5.0)                   |
+
+Tool rule fields:
+
+| Field              | Type     | Description                                                    |
+|--------------------|----------|----------------------------------------------------------------|
+| `required_bit`     | int      | Bit position that must be set in the user mask to use this tool |
+| `trigger_phrases`  | string[] | Phrases that start this tool call (blocked if bit not set)      |
+
+---
+
+## Package structure
+
+```
+reskSecure/
+  src/resksecure/
+    __init__.py              Public exports, version
+    policy_loader.py         YAML parsing, Policy/PolicySet models
+    trie_factory.py          Builds VectorizedAhoCorasick from a Policy
+    bitmask_processor.py     BitmaskLogitsProcessor (LogitsProcessor subclass)
+    tool_guard.py            Post-generation tool action verification
+    cache.py                 Thread-safe TTL cache for automata
+    policy_watcher.py        Hot-reload daemon that watches YAML mtime
+    config/example_policy.yaml
+  tests/
+  examples/
+```
+
+---
+
+## License
+
+This software is licensed under the RESK Software License. Commercial use requires a separate paid license. See the [LICENSE](LICENSE) file for details.
+
+For commercial licensing inquiries, contact: contact@resk.fr