How it works
Five stages, three areas, one loop
Nemesis runs continuous threat exposure management (CTEM) as a service. The same five stages repeat across your running systems, your code and your credentials, and every week ends in a written report.
The five stages
What Nemesis does
at every stage
Scope
- Running systems
- Targets agreed and authorized in writing.
- Code
- You connect repositories and set the policy.
- Credentials
- You share domains, key accounts and names to watch.
Discover
- Running systems
- Agents map the reachable surface and find weaknesses.
- Code
- Every commit and pull request is checked.
- Credentials
- New dark-web data is checked every day.
Prioritize
- Running systems
- Ranked by impact and by how weaknesses chain into attack paths.
- Code
- Only issues a change introduces can hold a pull request.
- Credentials
- Each alert carries its severity.
Validate
- Running systems
- Each finding is proven, then re-proven independently.
- Code
- A code finding can be proven on the running application.
- Credentials
- Each alert shows where and when your data appeared.
Mobilize
- Running systems
- Evidence and remediation on every finding.
- Code
- A suggested fix on the pull request.
- Credentials
- An alert in your portal with the steps to take.
All of it lands in one portal and one written report every week. Then the loop runs again.
One loop, three areas
Each area
has its own page
Running systems
Offensive security
Coordinated AI agents assess your live surface and prove what each weakness allows.
How offensive security worksCode
Code monitoring
Rule-based checks on every commit and an AI review on pull requests, with a suggested fix on each finding.
How code monitoring worksCredentials
Dark-web monitoring
Leaked accounts, exposed passwords and mentions of your company, checked every day across 15+ forums and marketplaces.
How dark-web monitoring works
Before we start
What we need
from you
A short setup for each area. Nothing is tested until the scope is agreed and you have authorized it in writing.
Running systems
Scope and written authorization
The domains, applications and services you want assessed, your written confirmation that you can authorize testing them, a testing window and a point of contact.
Code
Repositories to connect
Install our app on the repositories you want covered. It can read code, post checks and comments on pull requests, and open pull requests with suggested fixes. It never merges anything.
Credentials
Identifiers to watch
Your domains, the accounts that matter most, and your company and brand names.
What happens next
From first contact
to your first weekly report
Setup
Step 1: You request an engagement
Tell us what you want covered and when you would like to start, at nemesis.verixian.com/contact or geral@verixian.com.
Step 2: We reply
We reply by email to understand your environment and what you need covered.
Step 3: We agree the scope and the plan
We define the scope with you. You choose a plan, or a Starter Assessment of one domain first. Extras and custom plans are quoted.
Step 4: You authorize it in writing
Work starts only after that. Every client can sign our data processing agreement.
Step 5: You connect and share
On a plan, you connect your repositories, set your policy and share the identifiers to watch. Your organization invites its own people to the client portal.
Continuous
Step 6: The work begins
Assessment runs inside the agreed scope, your connected repositories are checked on every change, and dark-web monitoring starts.
Step 7: Your first weekly report
Findings, alerts and a written report reach you through your client portal. A new report follows every week.
Start here
Put verified findings
in your team’s hands
Tell us what you want covered. We will agree the scope with you and report what we prove, with the evidence, every week.