Operations | Monitoring | ITSM | DevOps | Cloud

OpenSearch is an open source search and analytics suite that developers use to build solutions for search, data observability, data ingestion, security information and event management (SIEM), vector database, and more. It is designed for scalability, offering powerful full-text search capabilities and supporting various data types, including structured and unstructured data. OpenSearch has rapidly developed into a standalone platform with unique features and capabilities.

Today, computers are more sophisticated, interconnected and complex than ever. This means they’re more capable than ever – but it also comes with a downside: that their attack surface is larger than ever, leading to an elevated risk of cyber incidents. Therefore, your approach to managing vulnerabilities needs to be holistic and prepare for all the ways in which vulnerabilities could cause damage to users, systems or your organization’s operations and reputation.

I always find the Olympics to be an unusual experience. I’m hardly an athletics fanatic, yet I can’t help but get swept up in the spirit of the competition. When the Olympics took place in Paris last summer, I suddenly began rooting for my country in sports I barely knew existed. I would spend random Thursday nights glued to the TV, cheering on athletes as they skillfully let fly arrows, disks, hammers and so on.

In the wake of EU drafted legislation and US executive orders, a software bill of materials (SBOM) has gone from a nice-to-have to a fundamental piece of software documentation. In this article, we’ll examine what an SBOM is, what information it must include, and the approaches that developers and manufacturers alike should consider as they start building their SBOM.

Typically, a technical writer takes the product created by a development team, and writes the documentation that expresses the product to its users. At Canonical we take a different approach. Documentation is part of the product. It’s the responsibility of the whole team. Documentation work is led by a technical author, who is part of the team, and whose title signals their technical authority.