Let me give you a quick introduction. My name is Stu Sjouwerman. I’m the Founder and CEO of KnowBe4, my 5th startup. I have been in IT for 40+ years, the last 25 of those in information security. In my last company we built an antivirus engine from scratch and combined it with intrusion detection, prevention and a firewall. And we ran into a persistent problem nobody seemed to be able to address; end-users being manipulated by bad actors to let them in.
SIEM (Security Information and Event Management) systems play a crucial role in modern cybersecurity frameworks. They collate log and event data from an array of sources within an organization’s network, facilitating real-time analysis and long-term storage of this crucial information to uphold security standards. A core component of SIEM’s effectiveness lies in its correlation rules, which are designed to detect specific patterns or anomalies that might indicate a security issue.
Firewalls are one of the most important cybersecurity solutions in the enterprise tech stack. They can also be the most demanding. Firewall management is one of the most time-consuming tasks that security teams and network administrators regularly perform. The more complex and time-consuming a task is, the easier it is for mistakes to creep in.
In the realm of cybersecurity, Security Information and Event Management (SIEM) systems are indispensable tools for monitoring and analyzing an organization’s security posture in real-time. However, one of the hurdles that security professionals often encounter is the prevalence of false positives which can overwhelm analysts and obscure genuine threats.
The variety of cloud services that store organizational data continues to proliferate in type and number leading to tension as more governments, policymakers, and organizations consider (or are in the process of) implementing mandates requiring that specific types of data remain within geographical borders. Many organizations need to navigate these data management compliance mandates while also satisfying the competing needs of expediency, cost-effectiveness and, of course, data security.
The story of how Tines scales starts in the product with, well, a story. Any user of Tines will be familiar with the basic concepts of actions and events. They know that when an action receives an event, it runs in order to, e.g., transform that event data or send it off to an API. They also know that when the action has finished running, it will usually emit an event containing its results – an event that will then be sent onwards, to other actions, causing them to run in turn.
This week, many institutions were targeted for attacks, impacting thousands differently. In the northeast of the US, New York’s gambling scene suffered an attack, downing casinos across the state. In the South, hackers attacked Florida’s Akumin clinics, exposing patient data. In Pennsylvania, the City of Philadelphia suffered from leaking the information of city email owners.
