Download the PHP package timeax/fortiplugin without Composer

FortiPlugin

FortiPlugin is a secure, policy‑driven plugin system for PHP applications. It fortifies your plugin ecosystem with install‑time scanning, signed packaging, and host‑enforced rules so third‑party code is verified, auditable, and under your control.

Fortified plugin system for PHP — secure packaging, validation, and install‑time policy enforcement.

✨ Key capabilities

• Install‑time scanner — Parse PHP into an AST and flag dangerous function calls, URL/file streams, path traversal, obfuscation hints, and high‑entropy blobs before anything is installed.
• Signed packaging — Embed a validation report, policy snapshot, and cryptographic signature inside each plugin archive.
• Host policy enforcement — Apply host‑defined rules both at build‑time (packaging) and at install‑time (re‑validation).
• Admin override with audit — Block by default; allow explicit overrides with full reports and tamper‑evident logs.
• Defense‑in‑depth — Optional runtime hardening (separate pools/containers, disable_functions, open_basedir).

🧭 Why FortiPlugin?

PHP is powerful and dynamic; uploaded plugins can hide payloads in non‑PHP files, comments, or encoded strings. Static scanning alone is not enough — policy must be enforced at packaging and again at installation. FortiPlugin brings that discipline:

• Treat plugins as untrusted until they pass scanning and signature checks.
• Keep a paper trail (validation report, signature, policy snapshot) with every build.
• Ensure the host remains the final source of truth for what is allowed.

🧱 Architecture at a glance

🔒 What the scanner looks for

Dangerous function calls (examples)

eval, assert, exec, shell_exec, passthru, system, popen, proc_open, dl, create_function, reflection‑based invocation.

Dangerous patterns

• Remote includes: include('http://...')
• Dynamic function variables: $f = 'e'.'val'; $f($code)
• URL/stream wrappers: php://, data://, zip://, glob://
• Path traversal: ../.., absolute sensitive paths (/etc/, /proc/)
• Obfuscation hints: long Base64, gzinflate(base64_decode(...)), chr() chains, XOR loops
• High‑entropy blobs or files with suspicious density vs behaviour

The scanner is extension‑agnostic. It inspects all files, not just .php.

🧩 Host policy (deny‑by‑default)

FortiPlugin applies a host‑owned policy configuration. At packaging time the developer’s tool fetches it; at install time the host re‑applies it. This makes policy centralised and versioned.

Example: security-policy.json

Philosophy: start from deny by default, allow with intent. Policy changes are audited and versioned.

📦 Package contents (signed)

A valid plugin archive typically includes:

• validation.log — detector matches, AST call map, heuristics,
• policy_snapshot.json — the host policy used at packaging time,
• plugin_fingerprint.sig — signature over the package/report.

🧪 Install‑time validation flow

1. Unpack to a staging area (no execution).
2. Verify the embedded signature & report against the host’s trusted key.
3. Rescan with the current host policy.
4. Compare to embedded results; if mismatched/new issues → block.
5. Decide: install if clean, otherwise require admin override.
6. Audit: log files, policy version, signature fingerprints, override rationale.

⚙️ Quick start (repo)

Install (dev):

Publish default policy (framework‑agnostic example):

If you don’t use the CLI, place your security-policy.json where your host expects it and point the policy server to it.

🧰 Minimal scanning example (PHP)

Illustrative snippet to show the approach (uses nikic/php-parser). Your implementation will be more robust.

🔏 Admin override (explicit & audited)

• Overrides are off by default and require an admin to confirm a review.
• The override record includes who, when, why, and the exact policy/report used.
• The plugin’s management UI shows a warning banner if installed via override.

🧮 Auditing & logs

For every installation attempt store:

• File list & hashes
• Flagged issues and AST call map
• Policy version & snapshot
• Signature fingerprints and verification status
• Whether an override was used (and rationale)

🧰 Optional runtime hardening

• Run plugins in separate PHP‑FPM pools or containers
• Set disable_functions & open_basedir
• Avoid dynamic include paths; never eval plugin code

📚 Terminology

• Policy: The host’s rules for what’s allowed, including tokens, dangerous functions, size limits, and class/method allowlists.
• Scan: Static analysis across all files (not just .php).
• Report: Machine‑readable log of matches, metrics, and timing.
• Signature: Cryptographic proof that the report and package weren’t altered.

🗺️ Roadmap

• Rich policy editor UI & diffing
• Deeper heuristics (n‑gram models, entropy thresholds per file type)
• First‑class Laravel integration (service provider, middleware, audit model)
• Marketplace protocol (capabilities, permission manifests)
• Revocation API & timestamp authority integration

🔁 Migration note (renaming)

This repository supersedes earlier drafts labelled “Secure Plugin”. All docs and identifiers are being migrated to FortiPlugin.

📄 License

TBD — choose a license that matches your distribution goals (MIT/Apache‑2.0/Proprietary). A LICENSE file will be added before tagging a stable release.

🙌 Contributing

• Open issues for bugs, naming, or policy defaults.
• PRs welcome for rules, detectors, and docs (include tests & rationale).

🧭 Maintainers

Timeax — security‑first plugin infrastructure.