What is our primary use case?
KnowBe4 is prominent in South Africa since 2016. I used it at Easy Pay, SARS (our tax authority in South Africa), and now at Capitec.
I have moved on from creating and simulating phishing emails since 2017. At the bank, we look after the infrastructure, licensing, and features. The junior compliance team helps set up simulations to catch people through Teams messages or links.
We must make the phishing emails better with the AI models that can be added through an extra license. The content must be very realistic so people can see the actual aftermath.
What is most valuable?
The scalability, integration, robustness of reporting and analytics, and user-friendly interface are valuable features.
KnowBe4 has improved significantly since we first acquired it at Easy Pay when I worked with a third-party vendor in India for setup. In my first simulation, I designed a menu for a year-end function, and half of the company clicked on it, requiring subsequent training.
Humans remain the weakest link. The analytics help us identify people who clicked, determine their training needs, and track progress. My personal statistics show I failed five out of 39 tests and reported 17, with a personal risk score of 47.4 and eight badges.
KnowBe4's AI integration has enhanced email authenticity. The model adapts to sending patterns. Recently, I was caught when I received what appeared to be an HR reply while waiting for a response. After returning from leave, I clicked on what turned out to be a phishing link.
The days of obvious scams are gone. Modern phishing emails appear authentic, as if from friends. This enables full-blown ATP operations using AI to generate convincing phishing emails, making it crucial to focus on AI-based detection against AI-generated threats.
What needs improvement?
As an architect who designs security solutions at Capitec, Africa's largest bank with 25-27 million clients, we must ensure good cybersecurity awareness for users.
There are gaps in overall security coverage. I rate KnowBe4 a 7 because improvements could be made beyond entry points and foothold perspectives. For instance, considering SQL injection vulnerabilities, more content should be provided for developers.
Adding a section specifically for developers would be beneficial, targeting that market as effectively as the organization-wide phishing email training. Organizations that have used KnowBe4 for years are developing good security habits.
KnowBe4 could educate people about OWASP Top 10 in web security testing and API security. Since OWASP Top 10 is open source, teaching these principles to keep organizations secure beyond Exchange server protection would be valuable.
For how long have I used the solution?
KnowBe4 has a significant presence in South Africa since 2016. I have used it at multiple organizations including Easy Pay, SARS (South African tax authority), and currently at Capitec.
What was my experience with deployment of the solution?
I use the on-premises version. The system experienced downtime during a patch or upgrade. The compliance team reported issues with creating simulations and pushing out training.
What do I think about the stability of the solution?
During the last downtime, it caused significant disruption as users couldn't access the system. Warren escalated this to a support ticket with KnowBe4. A representative from KnowBe4 South Africa, who is active on LinkedIn, previously gave a presentation at Capitec.
Which solution did I use previously and why did I switch?
I previously used OpenPhish, setting it up with Hive when building the open source SOC for SARS. This included ELK stack, Hive, MSP, and OpenPhish for creating phishing emails and fake domains.
At SARS, I attempted to implement KnowBe4 for three years. During RFQ processes for licensing, the pricing was considered too expensive under government procurement rules, though I disagreed with compromising on security.
How was the initial setup?
The setup process is straightforward. When implementing at SARS, we had assistance from a vendor, possibly Dimension Data. The basic setup involves server creation and software installation following documentation. My current role includes upgrading versions, .NET, and patching the Microsoft server as it's treated as a member server within Active Directory.
What about the implementation team?
The implementation at SARS was completed with assistance from a vendor, believed to be Dimension Data. KnowBe4 vendors in South Africa participated in the setup process.
What's my experience with pricing, setup cost, and licensing?
The solution was considered expensive, particularly in government contexts. However, security shouldn't be compromised as monetary considerations become secondary when security incidents occur.
What other advice do I have?
The system supports single sign-on integration. It's accessible through an internal internet where all applications are published. Users can access KnowBe4 through the apps portal using either username/password or single sign-on authentication.
The solution rating is 7 out of 10.
We maintain realistic training scenarios. Junior staff members create phishing emails with support available when needed. During system downtime, it significantly impacts operations, requiring escalation to KnowBe4 support.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other