mas-sentry-toolkit 0.2.1__tar.gz

mas_sentry_toolkit-0.2.1/.coveragerc

@@ -0,0 +1,14 @@
+[run]
+source = mas_sentry
+omit =
+    */tests/*
+    */lab/*
+    setup.py
+
+[report]
+show_missing = true
+skip_covered = false
+precision = 2
+
+[html]
+directory = htmlcov

mas_sentry_toolkit-0.2.1/.github/workflows/ci.yml

@@ -0,0 +1,93 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    name: Lint & type-check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install dev deps
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Ruff
+        run: ruff check .
+      - name: Ruff format
+        run: ruff format --check .
+      - name: Mypy
+        run: mypy mas_sentry
+
+  test:
+    name: Test py${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Pytest
+        run: pytest --cov=mas_sentry --cov-report=xml --cov-fail-under=70
+
+  security:
+    name: Security scan
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install bandit
+      - name: Bandit
+        run: bandit -r mas_sentry -ll
+
+  integration:
+    name: Integration (live broker)
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Start Mosquitto broker
+        run: docker compose up -d mosquitto
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Wait for broker on 1883
+        run: |
+          for i in $(seq 1 20); do
+            (echo > /dev/tcp/127.0.0.1/1883) 2>/dev/null && exit 0
+            sleep 1
+          done
+          echo "broker did not come up" && exit 1
+      - name: Integration tests
+        run: pytest tests/integration -v

mas_sentry_toolkit-0.2.1/.github/workflows/docs.yml

@@ -0,0 +1,31 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+    tags: ['v*']
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  build-and-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[docs]"
+      - name: Build site (strict)
+        run: mkdocs build --strict
+      - name: Deploy to GitHub Pages
+        if: github.ref == 'refs/heads/main'
+        run: mkdocs gh-deploy --force --clean

mas_sentry_toolkit-0.2.1/.github/workflows/release.yml

@@ -0,0 +1,68 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  build-and-release:
+    name: Build dists + SBOM
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install build tooling
+        run: |
+          python -m pip install --upgrade pip
+          pip install build twine cyclonedx-bom
+      - name: Build wheel + sdist
+        run: python -m build
+      - name: Check distributions
+        run: twine check dist/*
+      - name: Generate CycloneDX SBOM from locked deps
+        run: |
+          cyclonedx-py requirements requirements-lock.txt \
+            --output-format JSON \
+            --output-file dist/sbom.cyclonedx.json
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/*
+      - name: Attach to GitHub Release
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: softprops/action-gh-release@v2
+        with:
+          files: |
+            dist/*.whl
+            dist/*.tar.gz
+            dist/sbom.cyclonedx.json
+          generate_release_notes: true
+
+  publish-pypi:
+    name: Publish to PyPI (trusted publishing)
+    needs: build-and-release
+    if: startsWith(github.ref, 'refs/tags/')
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/mas-sentry-toolkit
+    permissions:
+      id-token: write
+    steps:
+      - name: Download dist artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - name: Drop non-distribution files (PyPI rejects SBOM)
+        run: rm -f dist/sbom.cyclonedx.json
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

mas_sentry_toolkit-0.2.1/.github/workflows/supply-chain.yml

@@ -0,0 +1,103 @@
+name: Supply Chain
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - pyproject.toml
+      - requirements.txt
+      - requirements-lock.txt
+      - .github/workflows/supply-chain.yml
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: "17 6 * * 1"  # weekly Mon 06:17 UTC - catch new CVEs in unchanged deps
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  lockfile-integrity:
+    name: Lockfile hash-verified install
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install runtime deps with enforced hashes
+        run: |
+          python -m pip install --upgrade pip
+          pip install --require-hashes -r requirements-lock.txt
+      - name: Install package (no deps)
+        run: pip install . --no-deps
+      - name: Import smoke
+        run: python -c "import mas_sentry; print(mas_sentry.__name__, 'ok')"
+
+  vuln-audit:
+    name: Dependency CVE audit
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install pip-audit
+        run: |
+          python -m pip install --upgrade pip
+          pip install pip-audit
+      - name: Audit locked dependencies
+        run: pip-audit -r requirements-lock.txt
+
+  dogfood-asi08:
+    name: Self-audit (mas-sentry ASI08)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install package
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e .
+      - name: Scan own lockfile for supply-chain risk
+        run: |
+          mkdir -p reports
+          mas-sentry agentic scan \
+            --target self-audit \
+            --requirements requirements-lock.txt \
+            --asi asi08 \
+            --out reports/self-asi08.json
+      - name: Gate on findings
+        run: |
+          python - reports/self-asi08.json <<'EOF'
+          import json, sys, pathlib
+          findings = json.loads(pathlib.Path(sys.argv[1]).read_text())
+          if findings:
+              print(f"::error::ASI08 self-audit found {len(findings)} finding(s)")
+              for f in findings:
+                  print(f"  - [{f['severity']}] {f['title']}")
+              sys.exit(1)
+          print("ASI08 self-audit clean: 0 findings")
+          EOF
+      - name: Upload self-audit report
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: self-asi08-report
+          path: reports/self-asi08.json
+
+  dependency-review:
+    name: Dependency review
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/dependency-review-action@v4
+        with:
+          fail-on-severity: high

mas_sentry_toolkit-0.2.1/.gitignore

@@ -0,0 +1,20 @@
+venv/
+__pycache__/
+*.pyc
+*.egg-info/
+dist/
+build/
+.env
+*.log
+reports/output/
+.DS_Store
+.idea/
+*.pcap
+*.bak
+site/
+.coverage
+coverage.xml
+.pytest_cache/
+
+# transient lab scenario run artifacts (curated demo/self-supply reports stay tracked)
+reports/lab_*.json

mas_sentry_toolkit-0.2.1/.pre-commit-config.yaml

@@ -0,0 +1,24 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-toml
+      - id: check-merge-conflict
+      - id: check-added-large-files
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.17
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.19.1
+    hooks:
+      - id: mypy
+        additional_dependencies:
+          - pydantic
+          - types-paho-mqtt
+        args: [--ignore-missing-imports]

mas_sentry_toolkit-0.2.1/CHANGELOG.md

@@ -0,0 +1,149 @@
+# Changelog
+
+## [0.2.1] - 2026-06-20 - First PyPI release
+
+### Added
+- `release.yml`: isolated `publish-pypi` job using OIDC trusted publishing
+  (`pypa/gh-action-pypi-publish`), tag-only, no API tokens. The package is
+  now installable from PyPI.
+
+### Notes
+- No runtime code changes from 0.2.0; this release exists to ship the PyPI
+  distribution path via the tag-triggered pipeline.
+
+## [0.2.0] — 2026-06-19 — Pivot to Agentic MAS Security
+
+### Changed
+- Relicensed from MIT to **AGPL-3.0-or-later** (sole contributor consent).
+- Repositioned: MQTT/AMQP-only → unified MQTT/AMQP **+ MCP + A2A + agentic** toolkit.
+- All findings now map to OWASP Agentic Top 10 (2026) in addition to STRIDE.
+- Python floor raised to 3.11.
+- CI badge URL fixed (user70616E6461 → evkir).
+- pyproject.toml migrated to hatchling backend.
+
+### Added
+- THREAT_MODEL.md (ASI01-ASI10, MCP CVEs, ABFP-STRIDE table).
+- CI matrix Python 3.11/3.12/3.13/3.14.
+- scripts/add_spdx_header.sh (idempotent, shebang-aware).
+- Pre-commit hooks (ruff/format) and Renovate dependency automation.
+- Integration tests against a live Mosquitto broker via docker compose.
+- Supply-chain security: hash-pinned `requirements-lock.txt`, `requirements.txt`
+  mirror with a drift-guard test, and `supply-chain.yml` CI (hash-verified
+  install, pip-audit CVE scan, ASI08 dogfood self-audit, dependency-review).
+- `docs/SUPPLY-CHAIN.md` documenting the pinning + verification model.
+- `release.yml`: wheel + sdist build, `twine check`, and a CycloneDX SBOM
+  generated from the locked deps, attached to the GitHub Release on tag.
+- CLI `--version` (via importlib.metadata) and documented shell completion.
+- `project.urls` Security + Threat Model entries for PyPI sidebar discovery.
+- Five verified usage example workflows under `docs/examples/`.
+- Dogfood ASI08 self-audit (`reports/SELF-AUDIT.md`) - 0 findings on the
+  hash-pinned lockfile.
+
+### Changed (hardening)
+- mypy is now a hard CI gate (previously advisory / continue-on-error).
+- ASI08 supply-chain scanner is pyproject-aware and ignores non-requirement
+  lines (option flags, `--hash` continuations, TOML scaffolding).
+- pytest config consolidated into `pyproject.toml` (asyncio auto,
+  strict-markers, coverage gate 60%); removed the shadowing `pytest.ini`.
+- Rewrote `ARCHITECTURE.md` and `docs/api/README.md` to the current
+  `UnifiedThreatEngine` module model; the old docs described the deleted
+  `SentryEngine` and shipped copy-paste examples that would ImportError.
+
+### Fixed
+- ASI08 parser miscounted TOML and option lines as dependencies, producing a
+  false "N/N unpinned" finding when pointed at a `pyproject.toml`.
+- ABFP report serialization of slotted `BaselineStatus` via `asdict`.
+- SARIF emitter no longer hardcodes the tool version; it is derived from
+  package metadata (importlib.metadata), so emitted reports never drift.
+
+### Removed (pre-release dead-code audit)
+- Pre-pivot `SentryEngine 1.0` MQTT/AMQP cluster: `core/engine.py`,
+  `core/session.py`, `core/config.py`, `core/display.py`, `core/exporter.py`,
+  `core/multi_target.py`, `protocols/auto_detect.py`, `agents/profiles.py` --
+  all superseded by `UnifiedThreatEngine` and the `reporting/` package.
+- Unwired SQLAlchemy persistence (`agents/abfp/storage.py`) and its
+  `sqlalchemy` + `alembic` runtime dependencies (alembic was a phantom dep:
+  no migrations, no alembic.ini).
+- Duplicate / unsafe ABFP fragments: `agents/abfp/stride_map.py` (duplicated
+  the live `abfp_stride_mapper`) and `reporting/abfp_html.py` (duplicated
+  `unified_html` without jinja2 autoescape).
+- Unwired ABFP features `agents/abfp/impersonation.py` and
+  `agents/abfp/graph_metrics.py`, deferred to v0.3.0 as properly wired+tested
+  modules (code preserved in git history).
+- Second divergent click CLI in `__main__.py` (sniff/abfp/fingerprint/walk/
+  audit/probe/learn/config) frozen at a hardcoded v0.1.0 banner and the
+  pre-pivot MQTT/AMQP command set; `python -m mas_sentry` now delegates to the
+  real `mas-sentry` CLI (mas_sentry.cli:app).
+- Net effect: real line coverage rose from ~66.9% to ~77% (dead 0%-modules
+  out of the denominator) and the runtime dependency surface dropped by two
+  direct + two transitive packages. CI coverage gate raised 60 -> 70.
+
+
+All notable changes to MAS-Sentry-Toolkit are documented here.
+Format based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+
+---
+
+## [0.9.0] - 2025-05-11
+
+### Added
+- Core Engine + CLI (5 commands: scan, abfp, report, probe, graph)
+- MQTT Analyzer — anonymous auth, wildcard topics, retained message poisoning
+- AMQP Analyzer — vhost enumeration, credential brute-force detection
+- Docker Lab — mosquitto broker + 3 MAS agents (sensor, actuator, coordinator)
+- ABFP Engine Phase 1: passive behavioral fingerprinting
+- ABFP Engine Phase 2: anomaly scoring (0–100)
+- ABFP Engine Phase 3: drift detection and alerting
+- Anomaly Detector — statistical baseline comparison
+- STRIDE Threat Mapper — automated threat modeling for MAS topologies
+- Report Generator — HTML, JSON, Markdown output formats
+- Active Prober — authenticated and unauthenticated probe modes
+- Interaction Graph — agent communication topology visualization
+- HCAP Protocol Specification v0.1
+- GitHub Actions CI — Python 3.10 / 3.11 / 3.12
+- Type aliases and typed helpers (core/types.py)
+- Coverage badge generator script
+
+### Fixed
+- numpy version pin for Python 3.13 compatibility
+- pydantic version pin for Python 3.13 compatibility
+
+### Infrastructure
+- pytest-cov integration with 70% threshold
+- pyproject.toml with mypy + ruff config
+- SECURITY.md vulnerability disclosure policy
+- ROADMAP.md with v1.0.0 milestones
+
+---
+
+## [0.1.0] - 2025-04-01
+
+### Added
+- Initial project scaffold
+- Basic MQTT connection probe
+
+---
+
+## [1.0.0] - 2025-05-13
+
+### Added
+- CVSS v3.1 calculator for MAS vulnerability scoring
+- IoT attack tree scenarios (AT-001, AT-002)
+- ROS2/DDS threat catalog (4 scenarios)
+- Threat scoring aggregation with risk level calculation
+- CONTRIBUTING.md with setup and commit guide
+- Full API reference docs
+- Attack scenario usage examples
+- STRIDE mapper tests, CVSS tests, aggregator tests
+
+### Changed
+- stride.py rewritten with threat_id, cvss_score fields
+- stride_mapper.py aligned with test expectations
+- numpy and pydantic version pins fixed for Python 3.13+
+
+### Tests
+- 116 commits, 100+ tests passing
+- CI green on Python 3.10 / 3.11 / 3.12
+
+---
+*Released: 2026-05-15*

mas_sentry_toolkit-0.2.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at ekiriyak@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

mas_sentry_toolkit-0.2.1/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing
+
+Thanks for considering a contribution. A few principles up front:
+
+1. **Scope.** This is a defensive/offensive security toolkit. We accept code
+   that helps detect, audit, or document risks against multi-agent systems.
+   We do not accept weaponised payloads or anything that helps attack systems
+   the operator does not own.
+2. **License.** All contributions land under AGPL-3.0-or-later. By opening a
+   PR you agree to license your contribution under this license. The author
+   retains copyright; commercial dual-licensing remains possible.
+3. **Style.** Run `ruff check . && ruff format . && mypy mas_sentry` before
+   pushing.
+4. **Tests.** New modules require unit tests. Targeted coverage minimum: 80%.
+5. **Commits.** Conventional Commits: `feat:`, `fix:`, `docs:`, `test:`,
+   `chore:`, `ci:`, `build:`, `refactor:`. Scope tags: `(core)`, `(mqtt)`,
+   `(amqp)`, `(mcp)`, `(a2a)`, `(abfp)`, `(agentic)`, `(threat)`,
+   `(reporting)`, `(cli)`, `(lab)`.
+6. **Active probes.** Any active-probe module must respect the scope guard
+   (`--confirm-scope` outside lab) and log to `~/.mas-sentry/audit.jsonl`.
+
+## Local dev
+
+    git clone https://github.com/evkir/mas-sentry-toolkit
+    cd mas-sentry-toolkit
+    python -m venv .venv && source .venv/bin/activate
+    pip install -e ".[dev,docs]"
+    pytest
+    ruff check .
+    mypy mas_sentry
+
+## Reporting security issues
+
+Do not open a public issue. Email `ekiriyak@gmail.com` with subject
+`[mas-sentry security]`.