The latest notable attack discovered on 2nd September 2024, occurred on the Cisco merchandise website. We explore the intricacies of the Cisco Magecart attack and what we know so far.

In today’s fast-paced development landscape, environments are no longer simple or isolated. You’re managing resources that span across development stages, geographies, and technologies. And as those environments grow more complex, so does the need for a more logical and efficient way to manage them.

It was 3AM at Newark Liberty International Airport. I was groggy, waiting in line to get my boarding pass, only to be met with a blue screen on the check-in kiosk. Needing some coffee, I learned the vendor was only accepting cash. There was clearly a big outage and I quickly checked our systems at PagerDuty. Major outages happen multiple times per year, so frequently that we have an internal dashboard (colloquially referred to as “the internets are broken”).

IT technical debt poses a significant risk to your organization’s cybersecurity. By understanding and managing IT technical debt, you can strengthen your organization’s resilience and ensure your IT infrastructure remains secure and efficient.

Security vulnerabilities are a serious issue for any organization. Even a single unpatched flaw can lead to disastrous consequences, including data breaches and loss of system integrity. CVE-2024-21410 is one such vulnerability that presents a significant risk. Found in a popular application used by many organizations, this flaw can leave systems exposed to attacks if not addressed promptly.

There is no escaping the discussion about how machine learning (ML) and AI systems will revolutionize how people and industries work. Most of this discussion needs to be revised, as companies are still evaluating how AI systems (typically Large Language Model (LLM) systems like OpenAI ChatGPT, Google Gemini, Anthropic Claude and others) enhance worker productivity and deliver business benefits. Cybersecurity is one sector where extensive use of AI-enhanced solutions is common.

Trace spans are captured in the runtime after decrypting the request. This means that any sensitive data is available in plain text. This is also the case for logging; however, logging requires an explicit log statement to be coded by the engineer. Additionally, engineers can add arbitrary information to trace spans, which could expose sensitive information. Collecting sensitive information in trace spans or logging events could expose an organization to a number of risks.

In recent years, regulations have been enacted that intend to ensure the continuity of essential services and mitigate security and availability risks. These regulations include the Digital Operational Resilience Act (DORA) and Network and Information Systems Regulations (NIS Regulations). In light of the recent incident involving CrowdStrike's Falcon system, it is legitimate to ask whether these regulations are truly effective.

There’s a users promise type for managing local users. However, did you know there is also a custom one for managing local groups? You might have seen it mentioned in the CFEngine Build announcement, the blog post on Managing local groups, or in the announcement supporting custom bodies post. But let’s take another look. The easiest way to integrate the groups custom promise type is by using cfbs, simply cfbs add promise-type-groups in your project.