Week 1–2
Mapping the terrain
We inventory every exposed service, dependency and access path. You receive a written picture of the attack surface before a single test runs — often the first complete map an organisation has seen.
Cyber defense practice · São Paulo
Nodo monitors, tests and hardens the infrastructure behind payments, logistics and public services. We work on the assumption that an attempt is already underway.
See how we work ›Security is not a product you install once. It is a practice you maintain — every release, every login, every quiet hour of the night.
— The principle Nodo was built on, 2014
A defined progression
Most engagements follow the same arc. We map the ground, find what an attacker would find, fix it in order of consequence, and stay watching once the work is live.
Week 1–2
We inventory every exposed service, dependency and access path. You receive a written picture of the attack surface before a single test runs — often the first complete map an organisation has seen.
Week 2–4
Our team works the way an intruder would: chaining small weaknesses into real access. Findings are reproduced step by step, so your engineers can confirm each one rather than take our word for it.
Week 4–7
We prioritise by consequence, not by count. A handful of issues usually account for most of the exposure; we fix those alongside your team and verify each correction with a retest.
Ongoing
From our monitoring centre we track behaviour around the clock. When something deviates from the baseline, a named analyst — not an automated ticket — looks at it within minutes.
What we do
Each engagement is scoped to your sector and the regulation you answer to — financial services, healthcare, logistics, public administration.
Structured, manual testing of your applications, networks and cloud accounts. Every finding arrives with reproduction steps and a remediation path your team can act on the same week.
Read the brief ›A monitoring centre staffed in São Paulo hours and overnight. We tune alerts to your environment so analysts spend their time on signals, not noise.
Read the brief ›When something breaks at 3am, you reach a defined team with a defined plan. We contain, recover and document — then walk you through exactly what happened and why.
Read the brief ›Practical alignment with the Lei Geral de Proteção de Dados and sector rules from the Banco Central and ANPD. We translate obligations into controls engineers can actually ship.
Read the brief ›By the numbers
How we hold ourselves
Common questions
If your question is not here, a short call usually answers it faster than a form.
A focused assessment of a single application or environment usually runs four to six weeks, end to end. Larger estates are scoped in stages so you see results early rather than waiting for one final report.
For most mid-sized organisations a retained practice costs less than a single senior hire, while giving you a full team across testing, monitoring and response. We are transparent about this trade-off — for some companies building in-house is the right call, and we will say so.
Yes. Nodo is incorporated in São Paulo under CNPJ 41.628.395/0001-72 and works within the Lei Geral de Proteção de Dados. We can sign the confidentiality and data-handling terms your procurement team requires.
Testing is scheduled with your team and bounded by rules of engagement agreed in writing. Where production risk exists, we work against a staging copy or within defined windows. You always know what is happening and when.
We retest the fixes at no extra charge within the engagement window, and we stay available for follow-up questions while your team works through the findings. Many clients then move onto continuous monitoring.
We do. A focused review of the systems that matter most is often more useful to a growing company than a sprawling audit. We will tell you honestly where the effort is worth spending.
Next step