{"id":212302,"date":"2024-04-01T12:15:19","date_gmt":"2024-04-01T12:15:19","guid":{"rendered":"https:\/\/www.techopedia.com\/?post_type=definition&p=212302"},"modified":"2024-04-01T12:15:19","modified_gmt":"2024-04-01T12:15:19","slug":"offline-signing-orchestrator-oso","status":"publish","type":"definition","link":"https:\/\/www.techopedia.com\/definition\/offline-signing-orchestrator-oso","title":{"rendered":"Offline Signing Orchestrator (OSO)"},"content":{"rendered":"

What is an Offline Signing Orchestrator (OSO)?<\/span><\/h2>\n

Offline Signing Orchestrator, also known as OSO, is an IBM cybersecurity<\/a> software product that allows cryptocurrency<\/a> transactions to be authorized in an offline environment before they are broadcast to an online blockchain<\/a> network. The enterprise-level software<\/a> allows digital assets<\/a> in cold storage<\/a> to be used in financial transactions without exposing private keys or needing to move assets online.<\/p>\n

IBM developed OSO in partnership with Metaco<\/a>, a digital asset custody provider owned by Ripple<\/a>. Currently, the software can only be used with IBM Hyper Protect Virtual Servers<\/a> built on IBM Z<\/a> and LinuxONE<\/a> mainframe systems.<\/p>\n

Techopedia Explains the Offline Signing Orchestrator Meaning<\/h3>\n

\"Techopedia<\/p>\n

IBM\u2019s full name for OSO is Hyper Protect Offline Signing Orchestrator<\/a>. In computing<\/a>, an orchestrator is programming that automates tasks and process execution in a controlled way.<\/p>\n

OSO was originally designed to provide air-gapped<\/a> transaction signing services for Metaco’s Harmonize Platform. The audit trails<\/a> that OSO provides are also helping the digital asset infrastructure<\/a> provider meet regulatory requirements.<\/p>\n

How Offline Signing Orchestrator Works<\/span><\/h2>\n

Offline Signing Orchestrator acts as an intermediary that manages communication between online and offline environments. It securely orchestrates transaction authorizations by isolating the digital signature<\/a> service.<\/p>\n

When deployed, the software will be installed on three logical partitions<\/a> that are referred to as LPARs:<\/p>\n