Communication is one of the hardest things to do well while responding to incidents. At FireHydrant, we’ve focused on helping people communicate well within their teams when responding to incidents, and also after the fact during post-incident reviews. But what about communicating with your customers? During an incident, your customers want to know that you’re aware of the problem and are working to mitigate or resolve it.
In IT security debates, projects aimed at managing access and identifying users are considered fundamental. However, the processes and technologies for controlling permissions have proved challenging. To solve this dilemma, what is now called Identity Access Management (IAM) was created, which involves the definition and execution of identification processes related to the most critical businesses for a company.
Since the outbreak of Covid-19, many organisations have had to make a swift transition to remote working to ensure business continuity. What would typically take months of planning and preparation was implemented in a matter of days. The chaos that this created, combined with the already uncertain nature of life during a pandemic, had created the ideal environment for cybercriminals.
July 03, 2020 We’re excited to announce a major enhancement to our platform: traces based alerts and metrics that better reveal the user experience and business performance. A trace tells the story of a transaction as it moves through multiple components of the system. A trace can show you the transaction components, and metrics tell you how the components are performing.
Hazelcast is a distributed, in-memory computing platform for processing large data sets with extremely low latency. Its in-memory data grid (IMDG) sits entirely in random access memory, which provides significantly faster access to data than disk-based databases. And with high availability and scalability, Hazelcast IMDG is ideal for use cases like fraud detection, payment processing, and IoT applications.
Permissions, access controls, user rights, or privileges define what an identity can see or do in an organization. These terms are often used interchangeably based on context, and essentially perform the same function—granting or denying access to the resources in an enterprise.
As a fast-moving startup, you don’t have the luxury of spending days figuring out exactly what you need in a Kubernetes cluster. We’ve been there. To help out, we wrote a whole ebook on the blueprint we followed as we built and deployed our own web app in Kubernetes.
Rightsizing an application is hard. Many applications are overprovisioned, running on more infrastructure than needed, to avoid failure when workloads grow. The alternative, an application crash when the load exceeds capacity, is also not acceptable to most users, developers, or businesses. The result, however, is unnecessary spending on idle resources during periods of low demand.
Information security (infosec) is a broad field. Its practitioners behave more like artists than engineers. After all, the mandate for security is not “do X”, but instead “ensure no one can do X, Y, Z, ɑ, β, ɣ, etc.”. The array of possibilities leading to infosec failure are vast. It’s like trying to prove a negative, thus making the task near impossible. On one hand we have an impossible task, on the other we have the affordance of time.
The first thing we tell Graylog users is, “Monitor your disk space.” The core set of metrics discussed below should always be in acceptable parameters and never grow over extended periods without going back to normal levels. This is why it is critical to monitor metrics that come directly from the hosts running your Graylog infrastructure.