We’ve listened, we’ve learned, and the market has definitely spoken! Our old name just wasn’t working: it was hard to pronounce, hard to spell, and hard to understand what we do. Even if the ‘archivist’ leap was made it didn’t carry our special mission with it.

One of my favourite tools for playing with REST APIs is, of course, Postman. It can make interacting with DataTrails super quick and easy, and help you develop custom workflows for storing and validating your digital provenance and audit trails. Here’s a step-by-step guide to getting a robust Postman set-up configured, and if you head over the Postman public collections you’ll find a link to a pre-baked DataTrails Postman collection with this done for you, along with some example requests.

Whether internally developed or purchased, your applications can be exposed to a host of vulnerabilities, especially via open source components that are widely used in today’s software. A recent survey found that 60% of data breach victims were compromised due to a known but unpatched vulnerability. Effective prevention and risk management requires being able to understand the vulnerability risk profile for each component of your Software Supply Chain.

In an increasingly interconnected world, the Internet of Things (IoT) has become a significant driver of innovation across various industries. Healthcare institutions were early adopters of IoT technology, leveraging it to improve patient care, streamline operations, and enhance data management. However, this surge in IoT adoption brings with it new challenges, one of which is the need for more transparency and security in the supply chain of connected medical devices.

Security Magazine reported more than 2,200 daily cyberattacks, which translates to roughly one cyberattack occurring every 39 seconds! As these stakes in cybersecurity continue to reach higher and higher levels, it becomes even more crucial to emphasize securing the very bedrock of elements upon which our digital existence is built.

The recent hype focused on the cURL vulnerability highlights the need for greater visibility and knowledge of your applications' software bill of materials (SBOM)