Contact
Aerial view of a city at night, with lit avenues and a bridge

Network and security, operated by those who design them.

We design, deploy and operate 24x7 the infrastructure of companies, internet service providers and datacenters.

Since 2012
in network engineering
+500
clients served
24x7
NOC and SOC with AI agents

The challenge

Having security tools is not the same as being secure. Firewalls, antivirus and switches generate alerts. Without a team watching, no one correlates, no one responds and no one measures. The alert arrives at night. Who responds?

You hire the operation up and running, not the tool.

No equipment investment

Equipment on loan with licenses included and replacement in case of failure or defect.

24x7 NOC and SOC team

No shift schedules, vacations or turnover to manage.

Metrics and management

Technical and executive reports on what was done and what changed.

Five fronts, one 24x7 operation.

Each front has its own design, deployment and operation. All of them share the same NOC, the same SOC and the same engineering.

Common foundation for all five fronts.

Operations room with a video wall and monitoring stations
NOC and SOC with AI agents24x7 operation that monitors the network and security of every front.
Technician organizing network cables in a rack
Network engineeringThe same team designs, deploys and evolves each environment.
Monitor in a dark room showing security monitoring data
Governance in SR64Tickets, changes and SLA recorded, with technical and executive reports.
Rack-mounted servers lit in blue
In-house productsNAC.SIS, RRBGP, GoDNS and RRBackup, developed by RR64.
night 00h06h12h18h 08:00

24 hours, every day.

  1. Business hoursThe NOC tracks links, servers and the changes scheduled for the day.
  2. Network changeDone with backup and change control, recorded in SR64.
  3. Your team goes homeThe operation continues exactly the same.
  4. Night-time alertThe AI agent summarizes and classifies the event. The SOC analyst responds.
  5. Before business hoursWhat happened overnight is already recorded for the report.

Saturdays, Sundays and holidays: the same operation.

How we work.

The company that designs the solution is the same one that deploys, operates and protects it, 24 hours a day.

IT professional using a computer in a server room
1. AssessmentWe map the environment, the critical points and the baseline.
Fiber optic cables connected to a patch panel
2. DesignWe define architecture, scope, SLA and support workflows, tailored.
Technician organizing network cables in a rack
3. DeploymentWe put the solution into production, documented.
Operations room with a video wall and monitoring stations
4. Active operationNOC and SOC handle events 24x7.
City skyline lit at night
5. GovernanceReports, SLA reviews and evolution recorded in SR64.

How we respond to an incident.

In the RR64 SOC system, every alert becomes a case. Analysts receive the case already correlated and identified by AI agents, which speeds up resolution.

  1. It becomes a caseAn alert from any tool enters the SOC system as a case, recorded from the very first minute.
  2. It arrives correlatedAI agents summarize, identify the type of event and cross-check it with the rest of the client's environment.
  3. The analyst resolves itWith everything identified, the analyst goes straight to the response agreed with the client. Business decisions remain with your company.
  4. It gets recordedEvery step stays in the case and goes into the technical and executive reports.

Illustrative example with fictitious data.

SOC caseIllustrative example · fictitious data
Case opened automaticallyUnknown device connected
SourceNAC.SIS
WhereAccess switch · port 12
AI agent analysisUnregistered device, outside the port profile. No other related alert in the EDR. Classification: unauthorized access.
ResponseDevice quarantined
DecisionAgreed with the client
RecordCase closed · goes into the report

Certifications for your network.

RR64 runs the assessment, adapts the network and requests the certification on the client's behalf.

KINDNS

Good practices for DNS operators

GoDNS already comes with the required security settings. RR64 adjusts the environment and requests the seal for the client.

KINDNS participant list

RPKI

Route origin validation

RR64 signs the client's BGP prefix announcements. Other networks start checking that those addresses really belong to the client, and a false announcement tends to be discarded.

MANRS

Norms for routing security

RR64 aligns the client's routing with the norms and handles joining the program.

MANRS participant list

Let's design the solution for your environment?

First we understand your environment. Then we design the solution, with no standard proposal.

E-mail
contato@rr64.net
Phone
+55 19 3825-7060
Address
Rua 13 de Maio, 720, Centro, Indaiatuba (SP), Brazil