swedencornet (TELOS/EOS Sweden) has same Network Layout for both “Telos” and “EOS Mainnet”. They both are part of EOSIO family.

Telos Setup:

EOS MainNet Setup:

swedencornet is applying industry best practices and fundamentally sound principals in Information Security and Privacy to protect EOSIO (Telos/EOS) Block Production operations.

Everything at swedencornet is based on Risks Management principles. Meaning that selection and application of information security controls and measures are based on risk profiles. The cost of security controls and measures should not exceed the risk exposure. swedencornet is focusing on protection measures that should make it impractical for the bad actors to harm (or cause damage) to the swedencornet block production infrastructure, systems and services.

Reference NW Layout for EOSIO Block Production based on Risk Profiles

Based on Risks Management sound principles swedencornet is planning to follow the three NW Layouts (pictured and described below). Environment will change (it is not static), technology will change, understanding and knowledge will change; and hence the Risks will change. So the NW Layouts (pictured and described below) and needed security controls and measures will change. We are living in a dynamic and agile world.

Network Layout and Deployment based on your Risk Profile

he best practice is to implement the network layout based on your risk profile and continuously adjust and improve it as threat profile changes. There is no one-fit solution for all Block Producers.

The 21 top Block Producers have different Risk Profile in comparison with other Block Producers (BPs) and they need tighten security controls and measures. The next range of standby Block Producers (BPs), let’s say from top 22 to 60, may have less risks and threats to coupe with while they are in standby. They may-not need same level of reliability and security as top 21 BPs. And then there is a whole different risk profile for the remaining standby Block Producer Candidates (BPCs). It does not make any justification and sense for a BPC, let’s say at nr 300, to implement and deploy network that supports same level of resiliency, fault tolerance, redundancy, and security measures that top-5 BPCs should have done it… But as the rank of BPCs goes up based on voting, the BPCs should be flexible enough to improve and enhance their capabilities in terms of scale-ability, reliability, agility and security.

The “BEST PRACTICE” is to implement and deploy the Network Layout based on your Risk Profile. So all there (3) layouts (pictured and described below) are best practices for the BPCs depending on which rank they have!

Note that one of the best practices, now-a-days, is that to use cloud services [whether it is Public Cloud, or Private on-premises Cloud (self owned and deployed Physical HW), or Hybrid]. Cloud brings lot of advantages in terms of scale-ability, reliability, agility and security. So at swedencornet we have taken the approach to go for cloud wherever practical (we may end up with Hybrid approach).

Basic NW Setup – EOSIO (TELOS/EOS) Block Producer:

 High Availability NW Setup – EOSIO (TELOS/EOS) Block Producer:

Extreme High Availability NW Setup – EOSIO (TELOS/EOS) Block Producer:

Social Networks for BP: swedencornet (TELOS/EOS Sweden)

6 votes, average: 4.67 out of 56 votes, average: 4.67 out of 56 votes, average: 4.67 out of 56 votes, average: 4.67 out of 56 votes, average: 4.67 out of 5 (6 votes, average: 4.67 out of 5)
You need to be a registered member to rate this.
(345 total tokens earned)
Loading...

Responses