New v1.2.79

Plexicus v1.2.79: Discard & Retry Remediations, Clearer Scan Failures, Team & Dashboard Fixes

Throw away a bad AI remediation and generate a fresh one, read clear failure reasons on every scan, and enjoy a smoother Dashboard and team management experience.

🚀 What’s New

  • Discard & Retry Remediations: When Codex Remedium produces a fix that isn’t what you needed, you can now discard it and start over. The remediation is permanently removed and its findings are released back to their pre-remediation state, so a new generation can pick them up immediately — no wasted findings, no need to contact support.
  • Repository Search Includes Forks: When adding repositories for scanning, the search results now include GitHub forks, GitLab group forks, and repositories across all your GitHub organizations. Forks that were previously invisible in search but visible in your repository list now appear consistently in both places.

🛠 Improvements

  • Clearer Scan Failure Reasons: Failed scans now show a concise, human-readable sentence explaining what went wrong — such as credentialsrefused, repositoryorbranchnotfound, or SCMhostunreachable — instead of raw tool output. The same clarity applies to failed-tool, clone, git-blame, aborted-scan, and truncation notifications across the Dashboard.
  • Last Admin Protection: You can no longer accidentally remove or demote the last remaining admin on your team. The platform blocks the action with a clear message, and the team page disables the Remove button and role selector for that user so the mistake can’t happen in the first place.
  • Organization Profile Validation: Required fields on the Settings → Organization form — Company Legal Name, Business Email, URL, and Category — are now enforced end-to-end. Incomplete submissions are rejected at the API level, so your organization profile always carries the information it needs.
  • Custom Dashboard Saves Cleanly: Saving a custom Dashboard layout no longer triggers a repeating save loop that could silently drop a widget you just added. Each edit saves exactly once and your layout stays the way you left it.
  • Accurate MitigatedExternally Display: Findings marked as mitigated externally now correctly show Yes in their details view — the field previously always read No regardless of the saved value.
  • Proper Language Tags on Every Page: Every page now ships with the correct attribute, so screen readers and browser translations work as expected across all locales.

🔒 Security

This release strengthens protections around remediation execution and platform access control:

  • Remediation tenant allowlisting: Codex Remedium can now be restricted to an allowlist of tenants, so only authorized accounts can run AI remediation. Unauthorized tenants see a clear temporarilyunavailable message and are never charged.
  • Sandboxed code execution: Jobs that run tenant-supplied code now operate under a dedicated, locked-down service account with no platform credentials and no elevated permissions, tightening isolation between tenant workloads and platform infrastructure.
  • Smarter credential handling: When an AI provider rejects a key or reports a fully spent plan, the platform immediately stops retrying against that credential and parks it, preventing unnecessary load and ensuring failures are surfaced promptly rather than silently retried for hours.

🔧 Fixes

  • Human false-positive verdicts preserved: When automated exploitation analysis runs, findings you manually marked as false positives are no longer flipped back — your human verdict always takes priority.
  • Legacy exploitation verdicts recognized: Findings from legacy scanning engines that report notexploitable are now correctly mapped to the live verdict system, so Reticulum exposure data stays accurate across engine versions.
  • Malformed IDs return clean errors: Invalid notification IDs and SBOM finding IDs now return a proper notfound response instead of an unhandled error, so the UI and API consumers always get a graceful answer.
  • Findings filter covers degraded enrichment: The findings filter now correctly selects findings whose LLM enrichment partially failed, so they no longer fall through the cracks when you’re triaging by enrichment status.
  • Enrichment usage attribution: AI usage records for finding enrichment now carry the finding, scan, and repository they belong to, so usage reports and cost attribution are complete and accurate.
Qualification

Check whether AI Swarm Pentest fits your environment.

Share the minimum context. We will review the scope and tell you the next commercial step.

Before submitting — verify you fit

0 / 280

No commitment. If you don't fit, we'll tell you.

SAMPLE HANDOVER · ILLUSTRATIVE

Sample evidence handover

A trimmed view of what your team receives at the end of an AI Swarm Pentest engagement. Real engagements include full technical evidence, executive narrative, and a remediation plan.

VALIDATED FINDING Evidence attached

Server-Side Request Forgery in webhooks/receiver

demo-project/sample-app · src/webhooks/receiver.py:42

SeverityHigh CVSS 3.18.6 Priority79 Confirmedvia replay

Untrusted caller-supplied URLs reach an internal egress without an allowlist. Replayed in a sandbox against a fresh authorized target — the same control was validated to fail twice.

REVIEWER-READY REMEDIATION Merge-ready PR

Validate the target URL against an allowlist of permitted hostnames. Reject private/internal IP ranges. Enforce HTTPS only.

plexicus/remediation/webhooks-ssrf 3 changed · 0 new files
42resp = requests.get(target_url)
42+if not is_allowed_host(target_url):
43+  raise WebhookRejected(target_url)
44+resp = requests.get(target_url, timeout=5)
Every engagement hands over:
  • Executive briefing
  • Validated findings list
  • Merge-ready PRs
  • Compliance mapping (NIS2 · DORA · CRA)
Private Round For investors