Skip to content
November 12, 2026
  • Bluesky
  • Facebook
  • Linkedin
  • Mastodon
  • RSS
  • Twitter
  • Youtube

Daily CyberSecurity

Zero-hour alerts. Unmatched analysis.

Primary Menu
  • Home
  • ADVISORIES
    • Microsoft
    • Fortinet
    • Ivanti
    • Cisco
    • Linux
  • CVE Data
    • CVE Watchtower
    • Top Exploited CVEs
    • CVE Stats by Vendor
    • Q3 2026 Report
    • CVE Alerts
    • CVE Alert Settings
    • Pricing
  • Cyber Criminals
  • Data Leak
  • Free Tools
    • CVSS 3.1 Calculator
    • Certificate Viewer
    • DNS Lookup
    • Encoder & Hash Generator
    • IP / Subnet Calculator
    • Whois Lookup
  • Malware
  • Vulnerability
  • Submit Press Release
Light/Dark Button
  • Home
  • Technique
  • Implementing the Four Eyes Principle for Key Security with Tatum
  • Technique

Implementing the Four Eyes Principle for Key Security with Tatum

Do Son October 23, 2022 6 minutes read
te

Source

Photo by CHUTTERSNAP on Unsplash

I watched a movie some time ago titled Fiery Priest. In that movie, there were four business colleagues who had kept their money in a safe. The safe had four locks, and the lock can only be opened with all four of their fingerprints.

So, if 3 of them wanted to stab the 4th in the back, they wouldn’t be able to do so because the fingerprint of the 4th person is equally needed. They wouldn’t be able to do so without some difficulty. This provides high security for their money and prevents anyone from betraying others.

An Example

Let us look at a scenario that people have faced while operating a business or setting up security protocols and how they addressed them.

Security is of crucial importance in the blockchain. Some decentralized organizations are member-owned. For them, ensuring that all members work towards a common goal can be difficult. Often different members may feel they know what is best and act on that impulse, against the better judgment of the others.

Using Signatures for Security

To prevent this, organizations have set it up so that a smart contract cannot be executed without the digital signature of each of the members involved in decision-making. Without the signature of each individual, the deployment or execution of the contract fails. This ensures that each stakeholder has veto power and no decision is taken without everyone’s approval.

Adding Qualified Persons to the List of Approvers

Another way you can set up your security protocol is by creating a qualified person panel that has to approve things. For example, companies can set it up so that the CEO, COO, and accountant need to agree before money can leave the company.

So, say the marketing head wants to try a marketing strategy. The CEO, COO, and accountant will need to agree to the plan before they can go ahead.

See a common theme till now?

These are all examples of a type of security principle called the ‘four eyes principle’.

The Four Eyes Principle

Source

The Four Eyes Principle means an activity or an action must be approved by at least two people. This is also called the two-man rule. This is to prevent actions that are not consented to and any fraudulent activity from an external person.

The main objective of this principle is to prevent mistakes while taking action, avoid fraudulent activity, and also ensure high security.

Now that we have a thorough understanding of the four eyes principle, let us see how we can enable it using the Tatum key management system (KMS).

Tatum Key Management System

The Tatum KMS is used to store private keys and mnemonics of the blockchain wallets securely. It runs locally on the server and provides security for wallets, addresses, private keys, and signing transactions.

This data is encrypted and stored on your server. It can only be decrypted by you using a password. A password is the most sensitive information in the system.

Installation

The Tatum KMS runs on different operating systems like Mac OS (natively or via docker), Unix (natively or via docker), and MS Windows(via docker only).

It can be installed via npm. Run the following code in your terminal:

npm i -g @tatumio/tatum-kms

As a docker image:

docker pull tatumio/tatum-kms

Usage

It is important to know how the KMS installed can be used so that you can tweak it as per your need.

To see all the commands available to run, you can use the help command:

tatum-kms –help

Tatum KMS periodically checks for any new pending transactions to sign and by doing this, it runs as a daemon by default.

The Tatum KMS checks for the pending transaction every five seconds. For every 500 signature IDs, 1 credit is consumed per API call.

Interestingly, the frequency of checking for transactions can be changed from 5 secs to any time you want using the –period command.

tatum-kms daemon –period=20

Tatum KMS uses the daemon memory to store data that are encrypted and the password to the wallet store. So after a successful set-up, the daemon requires the password to the wallet store.

bash:$ tatum-kms daemon
Enter password to decrypt wallet store:

The wallet store by default saves in the user’s home folder under .tatumrc the folder. To change the path to the wallet file, use the –path parameter.

Alternatively, the password can be provided via the environment variable.

tatum-kms daemon –path=/path/to/wallet/store/directory/wallet.dat

OR

TATUM_KMS_PASSWORD=password

By doing the above you have access to your data in the wallet store. For security, there is a need for the four eyes principle, which I have explained earlier.

The Tatum KMS checks for transactions on different supported blockchains BTC, BCH, BNB, LTC, ETH, ETH ERC20s, XLM, XRP, VET, DOGE, TRON, BSC, CELO, FLOW, XDC, EGLD. You can check for transactions with a different type of blockchain of your choice using the -–chain parameter.

tatum-kms daemon –chain=BTC,LTC,ETH

So, where does the four-eyes principle come in?

The four eyes principle can be enabled to verify that the transaction to sign with the KMS is yours.

To do so, the external-url parameter needs to be added and set up in your application server. The server should hold a list of valid transactions to sign. The external-url is very important on mainnet for security in the production environment.

Every time a transaction from Tatum is fetched to be signed, there is a validation against the external server using a simple HTTP GET operation.

tatum-kms daemon –external-url=http://192.168.57.63

Conclusion

Tatum KMS can help build and scale custodial apps, and also provide high security for users. More security can be attained using the four eyes principle, which is supported by Tatum KMS. There are different use cases for the Tatum KMS. Some of them are deploying smart contracts, minting NFTs, etc. You can get to know more use cases through their docs.

The Tatum KMS is a highly recommended platform for this because it allows you to use blockchain technology without having to deal with complex issues like private keys.

Search

CVE ALERTS
📈

EPSS Spike Alerts
Catch risk spikes before they make headlines.

🎯

Custom EPSS/CVSS
Set score thresholds to effectively filter noise.

🛡️

Exploit Intel
Real-world exploit signals beyond the KEV catalog.

🐙

GitHub Issues
Auto-create alert tickets without duplication.

📬

Weekly Digest
Clean summaries, eliminating email spam.

🏷️

Watchlist Groups
Tag vulnerabilities by team (Infra/AppSec/SOC).

🔀

Smart Routing
Route chat channels based on severity levels.

🚨

RBP Tracker
Early warning detection and tracking system.

Subscribe – $7/mo or try free for 14 days →

🚨 Active Exploits in the Wild

  • CVE-2026-20320CVSS 7.5
    A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote...
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-111793CVSS 4.3
    Openwave Webtop Media Transcoder does not enforce administrator-defined file type restrictions to restrict the file-types to be converted....
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-111560CVSS 8.6
    Improper neutralization of shell metacharacters in the timezone configuration field in certain Barracuda appliance products using common Barracuda...
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-116606CVSS 9.3
    An authentication bypass in Barracuda Email Security Gateway versions earlier than 9.4.0.030 allows an unauthenticated remote attacker to...
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-125350
    Use after free in XML. Reported by anonymous on 2026-11-06. Google is aware that an exploit for CVE-2026-125350...
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-124194CVSS 6.5
    Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to...
    CISA KEV📅 Added to KEV: Nov 10, 2026
  • CVE-2026-123751CVSS 9.8
    The WP Duplicate WordPress plugin through 1.1.11 does not properly verify a request authentication value and does not...
    Watchtower Verified📅 Updated: Nov 9, 2026
  • CVE-2026-114713CVSS 8.6
    The labeled-response module in UnrealIRCd 6.0.0 before 6.2.7.1 does not escape the IRCv3 "label" message tag when echoing...
    Admin intel📅 Updated: Nov 9, 2026
Powered by CVE Watchtower

Critical Vulnerabilities

  • CVE-2026-107935CVSS 9.3
    A path traversal vulnerability was found in gvproxy, the network forwarder provided by the gvisor-tap-vsock package. The unauthenticated...
    📅 Updated: Nov 12, 2026
  • CVE-2026-125883CVSS 9.3
    Improper restriction of XML external entity reference vulnerability in N-able N-central allows XML Schema Poisoning. This issue affects...
    📅 Updated: Nov 12, 2026
  • CVE-2026-76954CVSS 9.8
    An improper neutralization of special elements used in an SQL command vulnerability in the Auth API in Synology...
    📅 Updated: Nov 12, 2026
  • CVE-2026-126785CVSS 9.3
    A vulnerability has been found in rmalright TR-VISION HOME 2.0.5. Impacted is the function sub_11504 in the library...
    📅 Updated: Nov 12, 2026
  • CVE-2022-23851CVSS 9.8
    Netaxis API Orchestrator (APIO) before 0.19.3 allows server side template injection (SSTI).
    📅 Updated: Nov 11, 2026
  • CVE-2026-30530CVSS 9.8
    A SQL Injection vulnerability exists in SourceCodester Online Food Ordering System v1.0 in the Actions.php file (specifically the...
    📅 Updated: Nov 11, 2026
  • CVE-2026-34873CVSS 9.1
    An issue was discovered in Mbed TLS 3.5.0 through 4.0.0. Client impersonation can occur while resuming a TLS...
    📅 Updated: Nov 11, 2026
  • CVE-2026-36235CVSS 9.8
    A SQL injection vulnerability was found in the scheduleSubList.php file of itsourcecode Online Student Enrollment System v1.0. The...
    📅 Updated: Nov 11, 2026
Powered by CVE Watchtower

Daily CyberSecurity

  • About Daily CyberSecurity
  • Advertise with us
  • Announcement
  • Contact
  • Contributor Register
  • Login
  • Disclaimer
  • DMCA
  • Privacy Policy

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works

  • CVE Watchtower
  • CVE Statistics by Vendor 2026
  • Q3 2026 Report
  • Top Exploited CVEs
  • Bluesky
  • Facebook
  • Linkedin
  • Mastodon
  • RSS
  • Twitter
  • Youtube
© 2017 - 2026 Daily CyberSecurity. All Rights Reserved.