NexusVoid Argus
Connect Argus to Aegis with one two-way connection: Argus findings become risks and evidence in Aegis, a Secure Code check fails while a critical finding is open, and your framework scores flow back to Argus.
Argus finds and fixes security problems in your code. Aegis runs the program those fixes belong to. Connecting them turns two tools into one loop: Argus finds and fixes, Aegis proves it.
The connection works in both directions:
| Direction | Permission | What it does |
|---|---|---|
| Argus → Aegis | findings:read | Aegis reads your open Argus findings and a posture summary |
| Aegis → Argus | compliance:write | Aegis sends your framework scores back to Argus |
Aegis cannot change findings, start scans or read your code.
Connect Argus
Start in Aegis
Go to Security › Code Security and click Connect Argus, or open Integrations › NexusVoid Argus and connect from there.
Approve in Argus
You are taken to Argus, which asks you to approve the connection for your organization and lists exactly what Aegis will be able to do. Approving needs an Admin or Developer role in Argus.
Back in Aegis
You return to the page you started from. Aegis sends your framework scores to Argus straight away, then once a day.
The connection uses OAuth 2.0 with PKCE. Aegis stores the access it is granted in its encrypted credential vault, and the access tokens are short-lived and refreshed automatically.
If NexusVoid Argus is not available to connect on your Aegis account yet, it needs to be enabled for your organization first. Contact us and we will set it up.
What you see in Aegis
Security › Code Security shows your connected Argus:
- Open findings, with counts for critical, high, medium and low, the number of projects and when Argus last scanned.
- Open critical and high findings, up to the first 50, each with its severity, where it is (the project, file and line) and a link to the finding in Argus.
- Framework scores shared with Argus, with when they were last sent and a Sync now button.
Add a finding to your risk register
Any critical or high finding can be promoted with Add to risks. Aegis creates a risk in the Technology category with the finding's title, sets its impact and likelihood from the severity, and carries over the description, remediation, CVE, CVSS score, location and a link back to the finding in Argus. From there it is a normal risk: map it to controls, treat it, and track it with everything else in your risk register.
| Argus severity | Impact | Likelihood |
|---|---|---|
| Critical | Severe | Likely |
| High | Major | Possible |
Adding a finding needs permission to create risks. Each finding is added once: a finding that is already in your register shows In risk register with a link to its risk instead of the button, and adding it again returns the same risk rather than a duplicate.
Checks that use Argus
Connecting Argus adds two automated checks to your program:
| Check | Evidence for | Passes when |
|---|---|---|
| Argus Connected | Internal Security Audit | Aegis can reach your Argus organization |
| No Open Critical Code Findings | Secure Code | Argus reports no open critical findings |
No Open Critical Code Findings fails closed. If Argus cannot be reached, or does not return a count of critical findings, the check fails rather than passing. A control is never marked as met on an answer Aegis did not get. Once the critical findings are fixed in Argus, the check passes on its next run and the Secure Code task is evidenced.
What Argus sees
Aegis sends the same numbers it shows you, nothing recalculated:
- each framework's name and score, from 0 to 100
- how many policies are published, tasks are done and people have completed their requirements
- a link back to your frameworks in Aegis
Scores are sent right after you connect, every day at 06:30 UTC, and whenever someone clicks Sync now. In Argus they appear on the Compliance page, next to Open in Aegis. Each attempt is recorded, so if a send fails you see when and why in the sync box.
Disconnect
Disconnect from Integrations in Aegis, or from Compliance in Argus. Disconnecting in Aegis also revokes Aegis's access in Argus. Once disconnected, Aegis stops reading findings and stops sending scores. Risks you already created from Argus findings stay in your register, and the last scores Aegis sent remain visible in Argus.
If the connection stops working, for example after access is revoked on the Argus side, Code Security shows that it could not reach Argus. Reconnect from Integrations › NexusVoid Argus.
Next steps
Argus Overview
What Argus scans, and how it opens the fix.
Risk Management
Where promoted findings are treated.
Integrations & Cloud Tests
The other systems that keep your evidence current.
Penetration Testing
Connect Striker for pentest findings and reports.
Contact us
- Website: nexusvoidai.com
- LinkedIn: linkedin.com/company/nexusvoidai
- Email: ujwal@nexusvoidai.com