Crypto Market

Uppsala Security launches 2.0 version of its on-premise crypto threat management system » CryptoNinjas

Written by James Smith

Uppsala Security, a provider of advanced tools and services for crypto AML, KYC, transaction tracking, and regulatory compliance analytics, announced the release of TOMS 2.0, the new version of its Threat Reputation Database On-premise Management System, which was released at the end of March 2021.

The product was initially created to address the increased demand for on-premise solutions designed to meet the latest and strictest regulatory requirements in the digital assets space and through its new added features it provides even more efficient and seamless results.

Key features of TOMS 2.0 include up-to-date Threat Intelligence Data, flexibility when it comes to its integration — it can work with any organization, its applications, and services via a RESTful API and of course, as its name suggests, the on-premise characteristic, as it enables dynamic online access to the latest collective Security Intelligence data hosted in the Threat Reputation Database (TRDB) without any active internet connection on an organization’s internal computer network.

Regulations in the blockchain/decentralized ecosystem are gradually getting stricter and more specific on a worldwide scale. High-profile government agencies, financial institutions, and financial software applications that need to be compliant with the strictest regulatory frameworks are often required to adopt on-premise solutions in order to increase data privacy and security. By using a product such as TOMS, worldwide customers of Uppsala Security can not only enjoy access to the latest crowdsourced Threat Intelligence but can do so in a safe and on-premise, compliant environment.

The 2.0 version of TOMS comes with multiple improvements across different aspects, as follows:

1. Display of the download progress bar;

2. The current TRDB version available will be visible on the TMS screen (as the Datetime stamp);

3. There will only be a single frontend: TMS (the frontend of RTS has been merged with that of TMS so that the users no longer have to log in twice);

4. Auto sync settings are changed to a hh:mm format;

5. The auto-sync settings or manual trigger will check for any missing files and download, deploy to RTS and update the dB automatically (the missing files are checked between the last downloaded file and the latest TRDB version available);

6. Local TRDB Housekeeping

  • Full IOC and Update IOC File will be kept for 14 days;
  • The IOC File downloaded timestamp older than 14 days will be auto-deleted.


Source link

About the author

James Smith

Leave a Comment