Security Monitoring in Rwanda
Continuous monitoring for the signs of intrusion that a firewall alone won't catch.
Security monitoring is the continuous, active review of the signals your security tools already produce, so signs of an attack are spotted while there’s still time to act. Any organisation with security tools in place but nobody specifically watching what they report needs it. A firewall generates logs and endpoint protection generates alerts. Without someone reviewing them, most organisations only discover an incident once the damage is done, even though the evidence was there all along.
What is security monitoring, and who needs it
It brings together logs and alerts from sign-ins, devices, email, cloud services, firewalls and servers, applies detection rules that recognise suspicious patterns, and has someone triage what those rules flag. It suits organisations holding sensitive or regulated data, those that have already invested in security tools but lack people to watch them, and any organisation that couldn’t say today whether someone had signed in to an executive’s mailbox from another country last night.
The problem it solves
Many attacks don’t look like attacks to any single tool. A stolen password produces a normal-looking sign-in; a new mail rule silently forwards invoices to an outsider; a finance account downloads hundreds of files at 2am. Each event alone may raise no alarm. Monitoring connects them and turns quiet signals into an early warning, shortening the time an attacker has inside your systems.
Why detection speed now matters legally
Speed isn’t only a technical concern. Under Rwanda’s Law N° 058/2021 on personal data protection, a data controller must notify the National Cyber Security Authority within 48 hours of becoming aware of a personal data breach (Article 43). Rwanda’s national computer security incident response team, rw-CSIRT, set up in 2014, is the national point of contact for coordinating responses to security incidents. Institutions supervised by the National Bank of Rwanda also have incident reporting obligations under its cybersecurity regulation.
None of these obligations can be met without first knowing that something happened and what it touched. Good monitoring, and logs kept long enough, are what make a 48-hour notification realistic rather than a guess.
What we watch for
- Account compromise: sign-ins from unusual locations or devices, repeated failures, and multi-factor authentication changes.
- Privilege changes: new administrators, or changes to security settings.
- Email abuse: forwarding rules to outside addresses and mass sending.
- Data movement: unusual downloads or sharing of large numbers of files.
- Malware activity: detections on devices and attempts to disable protection.
- Perimeter events: VPN sign-ins, firewall threat detections, and connections to known-malicious destinations.
Equipment typically used
A central monitoring platform that collects logs and alerts, often Microsoft Sentinel or the Defender portal where Microsoft 365 is in use, or an equivalent security information and event management tool. Connectors for your firewall, VPN, servers and cloud services. Enough log storage to keep records for the agreed retention period, outside the systems being monitored. Nothing new is needed on staff devices beyond the endpoint protection they should already have.
What the work involves
- Agree scope: the systems, data sources and escalation contacts.
- Connect data sources to a central monitoring platform, and set log retention.
- Configure detection rules suited to your environment, then tune them to reduce false alarms.
- Define playbooks: what happens for each kind of alert, who is called, and what we may do on your behalf.
- Operate: alerts are triaged continuously within agreed hours, with monthly reports on what was seen and what should change.
What’s included and what’s not
Included: monitoring setup across your security data sources, detection rule configuration, and alert triage.
Not included unless bundled under a support agreement: hands-on incident response beyond initial triage and notification (see IT Support & Managed Services for broader support coverage).
Typical timelines and what drives cost
Initial setup typically takes two to four days, depending on the number of data sources, followed by a few weeks of tuning. Ongoing cost is a recurring fee driven by the number of users and devices, the data sources included, log retention, the coverage hours (business hours or round the clock), and how much response we perform on your behalf.
Common mistakes we see
Tools producing alerts that nobody reviews until after an incident. Alert rules left at defaults, generating so much noise that real threats are ignored. Monitoring only the firewall while sign-ins and email, where most attacks now begin, go unwatched. Logs kept for too short a time to investigate anything older than a few days. And no agreed escalation, so a genuine alert at night waits until Monday.
Cybersecurity
Related services
-
Cybersecurity Assessment
A structured review of your current exposure, ranked by real risk rather than a generic checklist.
-
Network Security
Segmentation, monitoring and controls that stop a single compromised device becoming a network-wide breach.
-
Firewall Configuration
Firewall rules and policies built around your traffic, not a vendor default left running for years.
Insights
Related reading
-
, 5 min read
The Network Security Basics Every Organisation Should Have
A short, concrete list of network security basics that apply regardless of industry or size — explained plainly.
-
, 4 min read
How Much Does IT Security Policy Development Cost in Rwanda?
Security policy development cost depends on policy scope, organisational input needed, and enforceability — here's what drives the number.
Frequently asked questions
Do we need our own security team to benefit from monitoring?
No. Monitoring can run as an ongoing service without in-house security staff. Alerts come to us for triage, and only genuine incidents reach your team, with clear instructions on what to do. If you do have IT or security staff, alerts can go to them as well, or instead, with us as backup out of hours. The arrangement is written into the agreement.
What actually gets monitored?
Sign-in activity, such as impossible-travel sign-ins, repeated failures and new administrator access; endpoint detections from your protection software; firewall and VPN logs; Microsoft 365 or Google Workspace activity like mail forwarding rules and mass file downloads; and, where relevant, server logs. The scope is agreed around the systems you run and the data that matters most.
How is this different from just having a firewall and antivirus?
A firewall and antivirus each block what they can and record what they see, but most organisations have nobody reading those records. Attacks that get past the first line, such as a stolen password used to sign in normally, show only as unusual patterns across several logs. Monitoring is the active layer that connects those signals and notices them early.
What happens when something suspicious is detected?
It's triaged for severity and likelihood. Routine noise is closed and recorded. A genuine threat is escalated straight away: under a support agreement we can take first containment steps, such as disabling an account or isolating a device, and otherwise we alert your named contacts with the evidence and recommended actions. Every incident ends with a short report on cause and fixes.
How quickly must a personal data breach be reported in Rwanda?
Under Rwanda's data protection law, a data controller must notify the National Cyber Security Authority within 48 hours of becoming aware of a personal data breach, and inform affected people where the risk to them is high. Meeting that deadline depends on detecting the breach and understanding what was exposed quickly, which is exactly what monitoring and good logs provide.
Not sure where your real exposure is?
Start with an assessment. We’ll show you which gaps matter most before you spend on anything.