Cybersecurity / Addis Ababa
Security that holds up when it matters.
We are cybersecurity specialists as well as builders. We secure the systems we build, and the ones you already run. If you are dealing with an active incident, call +251 911 418 196.
Most breaches are boring. An old dependency, a shared password, a backup nobody tested, an admin account nobody needed. We find those gaps and close them.
01 / Security work
Six ways we help.
Start with one review or keep us on call. Every engagement ends with a written report, a fix plan, and a retest where it applies.
Security audit and gap assessmentAccess / Cloud / Recovery
A structured review of your system, cloud, accounts, backups, and response plan. You get a ranked list, not a ninety page PDF.
Penetration testingWeb / API / Mobile
We test the way a real attacker would, inside a written scope. No production surprises, and a retest after the fixes.
Secure code and architecture reviewThreat model / Code / Review
We look for the mistakes that cause real breaches: broken access, exposed secrets, unsafe uploads, and missing checks.
Cloud and access hardeningIAM / Keys / Backups
We reduce admin access, remove shared passwords, turn on multi factor authentication, lock down storage, and test restores.
Incident response and recoveryContain / Recover / Learn
If something has already happened, we help contain it, recover, and write down what changes. Calmly and without blame.
Security training and tabletopTeam / Phishing / Drill
A short practical session for your team, plus a tabletop exercise for the day someone clicks the wrong link.
02 / What we check
The boring things that cause real breaches.
We do not start with a scanner. We start with how the system actually works, who can reach it, and what happens when a person makes a mistake.
Access
Who can see what, which accounts can change money or data, and how quickly access is removed when someone leaves.
Secrets
Passwords, API keys, and tokens that should never sit in code, screenshots, chat, or a public repository.
Dependencies
Old packages, unpatched servers, and third party services with more access than the job needs.
Recovery
Backups that have actually been restored, and a plan for the first hour of an incident.
Security is not a product you buy once. It is the discipline of closing the same small gaps before someone else finds them.
03 / How a review works
Clear scope.
Evidence, not fear.
We agree what is tested, what is off limits, and who is on call. You get a short report ranked by what can actually hurt the business.
Scope a reviewScope and rules
We agree what is tested, what is off limits, and who is on call. Testing production is a decision, not a default.
Week 1Map and test
We review access, dependencies, cloud settings, and the real screens and APIs your team uses.
Week 1 to 2Write the report
A short report ranked by impact. Each finding has evidence, the possible damage, and a plain fix.
Week 2Fix with your team
We work with your developers, or take the fixes ourselves when you want us to.
Week 2 to 4Retest and monitor
We confirm the fix, not just the ticket, and leave alerts and monitoring in place.
Week 4 and beyond04 / Built in
We do not bolt security on at the end.
Every system we build gets the same baseline: least privilege access, audit trails, encrypted data, tested backups, dependency checks, and a written handover. The same discipline applies to systems we did not build.
Ask about a security review05 / Questions
The things people ask first.
If your question is not here, send it. We answer security questions in plain language.
Do you test production?
Only with written permission. We prefer a staging copy, but some access and configuration checks have to happen on the real environment. We agree the rules first.
Can you help after a breach?
Yes. Call +251 911 418 196. We help contain the incident, protect accounts, recover data, and write the changes that stop it happening again.
Do you work on systems you did not build?
Yes. Most security work starts with a system someone else built. We review what is there and do not require a rebuild.
How long does an audit take?
A focused review takes about two weeks. A full web and API test with a retest usually takes three to four weeks, depending on scope.
Do you provide a certificate?
We provide a written report, evidence, and a retest. We do not sell a badge. If you need ISO 27001 or another formal certification, we help you prepare and work with the auditor.
What does the report include?
A ranked list of findings, how each one could be used, the evidence, and a plain fix. We also include what we could not test and what still needs a decision.
Next step
Find the gaps before someone else does.
Tell us what you are running and what worries you. We will tell you what a review looks like and what it costs.