Patent ID: 12190387

NOMENCLATURE

The following nomenclature is used in this patent application:AML—anti-money launderingATS—alternative trading systemB2B—business to businessB2C—business to consumerC2C—consumer to consumerC3C—three smart contract applicationsCCL—C3C CloudLedgerCS—cybersafetyCSC—C3C smart contractCSR—common reporting standardCTP—C3C token platformCTS—C3C transaction systemGRC—governance-risk-complianceIP—internet protocolIT—information technologyKYC—know your customerPORT—permission of risk transferPORT—proof of risk/transfer/timePOS—proof of stakeSDN—software-defined networkSTO—security token offeringUI—user interfaceUID—unique identifierUX—user experience

DETAILED DESCRIPTION OF THE INVENTION

The token platform of this invention is massively scalable, secure, private-public, insurance-industry friendly that assists in the underwriting of cryptocurrency transactions. In the blockchain of this invention, transactions involve the transfer of quantifiable risk, while in other blockchains, transactions may involve the transfer of any asset or a record of some service being rendered. The smart contract that includes the blockchain of this invention provides the policy language of the transaction that allows the ledger state to be modified.

Consensus in the network refers to the process of achieving agreement among the network participants as to the correct state of data on the system. Consensus leads to all nodes sharing the exact same data. A consensus algorithm, hence, does two things: (1) it ensures that the data on the ledger is the same for all the nodes in the network, and, in turn, (2) prevents malicious actors from manipulating the data. The consensus algorithm varies with different Hyperledger (blockchain) applications.

The first row20in the table relates to the customer. The customer starts compliance registry suite module22in the customer row20receives input data from the customer log in module42. The initial application is started when the customer starts compliance registry suite module22sends output data to the customer orders cybersafety premium report module24. The customer starts compliance registry suite module22also sends question and answer data to the free CRS profile report module44.

The customer orders cybersafety premium report module24in the customer row20receives input data from the customer starts compliance registry suite module20, the free CRS profile report module44and the customer wishes to re-engage their cybersafety profile module30. The customer orders cybersafety premium report module24sends output data to the CRS customer requests CS/IP data insurance module26and output yes data to the premium cybersafety fee module62.

The CRS customer requests CS/IP data insurance module26in the customer row20receives input data from the customer orders cybersafety premium report module24and the cybersafety premium report module46. The CRS customer requests CS/IP data insurance module26sends output data to the CRS customer interacts with master policy form module48.

The customer accepts master policy approved terms module28in the customer row20receives input data from the CS/IP master policy account module64and the calculate master policy escrow terms module88. The customer accepts master policy approved terms module28also receives yes input data from the terms of approval module90.

The customer accepts master policy approved terms module28sends output data to the master policy terms of coverage enforcement module50and the CS/IP master policy escrow module66.

The customer wishes to re-engage their cybersafety profile module30in the customer row20sends output data to the customer order cybersafety premium report module24.

The second row40in the table relates to UI/UX. The customer log in module42in the UI/UX row40sends output data to the customer starts compliance registry suite module22. The free CRS profile report module44in the UI/UX row40receives question and answer data from the customer starts compliance registry suite module22. The free CRS profile report module44sends data to the customer orders cybersafety premium report module24.

The cybersafety premium report module46in the UI/UX row40receives payment data from the premium cybersafety fee module62. The cybersafety premium report module46sends output data to the CRS customer reports CS/IP data insurance module26, the CS/IP master policy account module64, the KYC/AML analysis module82, the analyze compliance scores module84and the compliance criteria analysis module102.

The CRS customer interacts with master policy form module48in the UI/UX row40receives input data from the CRS customer requests CS/IP data insurance module26and sends initiate output data to the CS/IP master policy account module64.

The master policy terms of coverage enforcement module50in the UI/UX row40receives input data from the customer accepts master policy approved terms module28. The master policy terms of coverage enforcement module50sends output escrow fee data to the CS/IP master policy escrow module66.

The not approved module52in the UI/UX row40receives no data from the terms of approval module90.

The third row60in the table relates to CS/UID fee. The premium cybersafety fee module62in the CS/UID fee row60receives yes input data from the customer orders cybersafety premium report module24. The premium cybersafety fee module62sends payment data to the cybersafety premium report module46. The premium cybersafety fee module62also sends data to the KYC/AML analysis module82.

The CS/IP master policy account module64in the CS/UID fee row60receives input data from the cybersafety premium report module46, the CRS customer interacts with master policy form module48and the credit analysis and terms module86. The CS/IP master policy account module64sends output data to the customer accepts master policy approved terms module28and the calculate master policy escrow terms module88.

The CS/IP master policy escrow module66in the CS/UID fee row60receives input data from the customer accepts master policy approved terms module28and the master policy terms of coverage enforcement module50. The CS/IP master policy escrow module66sends data to and receives data from the IT event micro-policy fees module68in the CS/UID fee row60. For example, the IT event micro-policy fees module68sends debit data and credit data to the CS/IP master policy escrow module66. The IT event micro-policy fees module68also receives data from the claims adjudication and limits module112.

The fourth row80in the table relates to analysis. The KYC/AML analysis module82in the analysis row80receives output data from the premium cybersafety fee module62and the compliance criteria analysis module102in the underwriting row100. The KYC/AML analysis module82also receives output data from the cybersafety premium report module46. Output data from the KYC/AML analysis module82is sent to the analyze compliance scores module84.

The analyze compliance scores module84in the analysis row80also receives input data from the cybersafety premium report module46. The analyze compliance scores module84sends approval output data to the credit analysis and terms module86. The analyze compliance scores module84also sends CRS score data to the credit analysis and terms module86.

The credit analysis and terms module86in the analysis row80also receives output data from the network risk analysis module106. Output data from the credit analysis and terms module86is sent to the CS/IP master policy account module64. Output data from the credit analysis and terms module86is also sent to the calculate master policy escrow terms module88.

The calculate master policy escrow terms module88in the analysis row80receives output data from the CS/IP master policy account module64and ok output data from the credit analysis and terms module86. The calculate master policy escrow terms module88sends output data to and receives input data from the master policy underwriting analysis report108.

The calculate master policy escrow terms module88sends output data to the customer accepts master policy approved terms module28and to the CS/IP master policy escrow module66. The calculate master policy escrow terms module88also sends output data to the terms of approval module90in the analysis row80.

The terms of approval module90in the analysis row80receives input data from the calculate master policy escrow terms module88and the master policy underwriting analysis report108.

The terms of approval module90sends yes output data to the customer accepts master policy approved terms module28, the loss control module110and the claim adjudication and limits module112. The terms of approval module90sends no output data to the not approved module52.

The fifth row100in the table relates to underwriting. The compliance criteria analysis module102in the underwriting row100receives input data from the cybersafety premium report module46. Output data from the compliance criteria analysis module102is sent to the KYC/AML analysis module82and the determine eligibility module104.

Output data from the determine eligibility module104in the underwriting row100is sent to the network risk analysis module106in the underwriting row100. Output data from the network risk analysis module106in the underwriting row100is sent to the master policy underwriting analysis module108and to the credit analysis and terms module86.

The master policy underwriting analysis report module108sends output data to and receives input data from the calculate master policy escrow terms module88. The master policy underwriting analysis report module108also sends output data to the terms of approval module90.

The loss control module110in the underwriting row100receives yes output data from the terms of approval module90. The loss control module110sends output data to and receives input data from the claims adjudication and limits module112.

The claims adjudication and limits module112in the underwriting row110also receives yes output data from the terms of approval module90. The claims adjudication and limits module112also sends output data to the IT event micro-policy fees module68.

Within the context of data and governance, regulation and compliance, blockchain can be used to drastically improve security and decrease dependency on central entities. Since the digitization of business processes nearly two decades ago, most enterprises have come to rely on remote databases and the interconnected devices to properly function on a daily basis.

By introducing blockchain data insurance, governance, regulations and compliance monitoring, companies can benefit from reliable databases on decentralized, encrypted and non-editable ledgers, embracing the full potential of the technology to streamline and secure their data storage. The consensus required for modification of the blockchain code as well as the ledger's distribution only serve to add to the safety and inviolability of the data stored on it. Integrating blockchain technology for example for cloud computing services will help enterprises maintain their competitive advantage by protecting valuable business intelligence, while encrypted nature of the blockchain can be used to protect networks of interconnected devices from external interference.

Understanding the hurdles to adopting governance within cloud-based services is also another challenge facing companies. At the top of the list is the resistance from internal IT teams to embrace this new way of working. Despite the clear business drivers for change (flexibility, agility, resilience, automation, cost effectiveness) and clear demand from senior business stakeholders, IT teams are still resistant to cloud services. The passing of responsibilities over to a third-party (service) is perceived as insecure because data would be leaving the building that leads to more complex governance issues.

There are two key regulatory roles. The first is the protection of personnel private information. The second is the role that government (regulation) plays is the legal enforcement of contractual obligations. We need to expand upon the second role in the deployment of smart contracts. When parties agree to a contract they are incentivized to stick to the contract because of the potential legal implications of reneging. Without the threat of legal repercussions, there would likely be a high percentage of unfulfilled contractual obligations. Such a situation would affect commerce as well as civic relationships.

However, blockchain provides digital self-enforcing cyber insurance contracts widely known as smart contracts. The stipulations in a smart contract are hard-coded into its software meaning the smart contract only executes once all policy requirements are met.

The unique self-regulatory functionality features of the C3C will allow cross cybersecurity and/or cybersafety industry barriers to be successfully implemented into any insurance market.

Features of this process include:Low commission fees for conversion of C3C token into fiat currency andvice versa;Lower risks of financial volatility;In case of arbitration process, the refunds and the set penalties may be reimbursed at the same value as at the start of the arbitration process, avoiding devaluation of C3C tokens in question.Underwriting value of the secure risk transfer feature of the transaction, may also be regulated by the C3C token value.

These unique features of the C3C token will allow the token to cross cybersecurity and/or the cyber-safety industry barrier and be successfully implemented in any other insurance market. According to Christine Lagarde, the Managing Director of the International Monetary Fund “a cryptocurrency that has self-regulatory feature can provide conventional government-issued tenders a “run for their money”. In addition, C3C transaction system may fully support C3C token-based loyalty and partner programs available to all participants of CTS financial ecosystem.

CTP will solve issues with transaction fees, private keys, alphanumeric addresses, arbitration, and cyber security issues that impede mainstream users from holding a cryptocurrency. This invention makes the on-boarding process fast and hassle-free; users will not require experience with cryptocurrencies to use CTS or utilize C3C tokens.

Calculation of a cybersafety score begins with the value of between about 0.00 and 1.00 that is a measure of an organization's regulatory compliance environment based on its demography, class-of-trade profile, size of operations and business compliance requirements. Companies that develop, manufacture, market, and sell services and products anywhere in the world, must develop internal risk controls and procedures that promote adherence to applicable statutes, and regulations of data privacy and security programs in evaluating and, refining existing compliance programs to ensure regulatory compliance.

Additionally, the cybersafety score serves as the benchmark or comparison against which to measure ongoing GRC efforts in an organization or a comparison to similar organizations in the same sub-class of trade or geography or cyber risk management practice. Risk officers shall soon be able to proactively manage business operations and compliance in a single uniform platform regardless of business vertical or complexity. For the first time, the cybersafety methodology shall enable companies to evaluate their potential exposure of the various cyber-risks and develop proactive measures to minimize that risk. Moreover, the CS methodology is compatible with the rapidly expanding software-defined IT service class of business.

The platform enables the building of custom IT service recipes for multi-orchestration, providing a multi-client management interface for enterprise IT teams. The platform can identify incremental IT event's value@risk exposure, prior, during and following. These IT events can be proactively risk scored and underwritten enabling real-time nano-insurance, blockchain-based C3C smart contracts.

C3C Token Platform

The C3C token is a multi-tier blockchain platform that encompass three cyber risk functions: 1) cyber risk event identification token; 2) cyber risk control blockchain; and 3) cyber risk transfer blockchain.

The C3C will enable the securitization of the underlying ‘value of risk’ of the CTP. C3C tokens may be able to provide an array of financial rights to the user/holder, such as equity, dividends, profit share rights, voting rights, and buy-back rights pegged to the ecosystem's value. The C3C token represents a right to the asset value attributed to the company overseeing the ecosystem, such as profits, cash flow, reinsurance holdings and investment capital returns. Rights may be written into the C3C smart contracts and C3C tokens will be allowed to be traded on SEC compliant exchanges as financial securities.

Following the completion of the STO and satisfaction of “know-your-customer” protocols, the C3C security token generation will follow. The securitized token will be available for use on the CTP. The C3C token framework has monetary value within the CTP network, as a tradable security asset on future ATS/exchanges. The value, however, may be converted into fiat currency via an approved C3C wallet.

Additionally, C3C value can be used to pay for other risk transfer services offered within the ecosystem, including risk services with participating telos, cloud service networks and insurance services worldwide. Once again, the C3C securities value may be pegged to the company's overall profit, and revenues directly earned for engagement on network. Although the price of C3C's may increase with time, such an increase is not guaranteed and should not be reason enough to acquire C3Cs.

Finally, the invention introduces a more efficient transaction insurance derivative of the greatly anticipated C3C protocol, before any B3i insurance blockchain. C3C will be unique in the fact that it is based on proof of PORT i.e., proof of premium, as opposed to proof of stake and/or proof of work. C3C PORT has the primary benefit of dramatically reducing the amount of risk over time and energy required to operate super-efficient, lightning fast blockchain transactions, reducing both fixed and variable costs, as well as ensuring that the blockchain remains scalable and sustainable.

C3C Token Acquisition

C3C tokens can be acquired by purchase, earning, trading, and participating in CTP programs. Individuals will have an option to purchase C3C tokens via one or more of the following:

Trading on the cryptocurrency exchange;Trading on a crypto-settlement exchange;Directly from holders of C3C tokens;Directly from the company via the C3C wallet;During pre-sale STO events

Furthermore, C3C tokens can be earned by active service members participation utilizing CTP. Simply through engagement on CTP, service (node) can be converted to C3C utility tokens using the cryptocurrency wallet. The membership (value) can be earned within the ecosystem as well as through partnering networks. This process will expand the C3C token usability, providing limitless economic possibilities for all parties involved. C3C tokens may also be acquired through peer-to-peer auctions. Lastly, users can obtain C3C tokens by participating in loyalty programs offered by insurance carriers. The collected tokens can be exchanged for goods and services with participating insurance partners and additional technology products, including cloud exchange services and SDN consultants.

C3C Token Use

After C3C token generation event, individuals and businesses alike can use C3C tokens to do one or more of the following:Pay for risk transfer services;Pay for insurance partner membership;Pay for technology partner membership;Pay for sponsored membership and other risk marketing products offered by the C3C token platform.Exchange tokens for cryptocurrencies e.g. Bitcoin, using a crypto-exchange;Use C3C token to pay for insurance products-services via partner platform network;Exchange tokens for goods and services using the C3C token platform;Transfer C3C tokens between users (peer-to-peer) B2B, B2C, and C2C.
C3C Token Risk

Individuals and businesses should observe and respect the risks according to one or more of the following:C3C token is not currency, issued by any national, supra-national or central bank;There are multiple factors that may directly or indirectly influence the value of C3C that may not be within control of the C3C token platform and/or the associated company;C3C token is not in any way backed by any hard assets or other credit;Trading C3C tokens will depend on consensus of value@risk among market participants;At any given time, there may be no available market for C3C, nor buy and sell C3C;No one is obligated to purchase any C3C from any holder of C3C.
C3C Risk Transfer Platform

The CRT is the specific risk transfer tracking mechanism that allows C3C users to conduct financial risk operations with the C3C's cyber “risk-transfer” token. The CRT is the community of all risk transfer entities, participants, technical services, node connectivity and the decentralized nature of the C3C protocol that are connected by common economic interest that specifically include data's risk.

The invention solves the financial setbacks of tracking a risk IT event on an incremental basis faced by the [cyber] insurance industry. The CRT platform may function as an autonomous cross-chain/side-chain, and may be established as a risk-monetary exchange, set to run as a self-regulating decentralized blockchain. The CRT may exist autonomously regulated by the CRT blockchain participants. The CRT may incorporate a digital escrow wallet and be accessible per membership. In addition, C3C tokens may be converted into fiat-based currency via online digital exchange or an ATS.

The CRT platform will have the following features: secure sale, C3C token withdrawal, debit/credit claims and arbitration mechanisms. The CRT platform may operate as a permissioned blockchain and thereby be regulated by all participants of the C3C blockchain. The CRT platform will not generate profit by itself, as it will be fee-less to operate. However, the underlying C3C will possess securitized value due to its risk transfer value purpose.

The CRT may serve as a marketplace for multiple other insurance-related product-lines as well, which may be offered according to the entity's data risk standard protocol that may be interoperable amongst multiple service features. Such integration will allow mainstream users to use C3C tokens at any insurance service in the near future. Subscribers will be able to use C3C tokens as a transaction medium to purchase additional insurance products and pay for cloud services including telco services benefiting from enhanced security and arbitration mechanisms.

C3C Risk Transfer

To protect C3C risk transfer, “Buyer” (the “Risk Purchaser” or “Customer”) and “Seller” (the “Risk Acceptance” or “Insurance Entity”) engaged in online transactions involving a C3C token. The CRT is programed with the CSC that include escrow, risk asset valuation, arbitration, adjudication and appeal services for each policy in CRT. The CRT platform will aim to reduce fraud while stimulating the C3C Insurance blockchain to build trustworthiness.

The C3C network escrow service is designed to benefit the customer, ensuring fulfillment of promises outlined by the CSC insurer. The funds payable by the customer upon purchasing of a risk asset which may be held by the C3C system in escrow until the risk transfer is successfully performed by forensic ledgering each transaction in real-time then reconciling the customer's entire data history at the end of each month—i.e., updating the C3C blockchain periodically, not with every transaction.

The system may use sophisticated tracking and client feedback mechanisms to confirm validation of risk transfer service within allocated PORT validation. Once the customer auto-confirms receipt of data, the C3C's risk transfer funds (proof of premium) is released by the system, and transferred to the entity's C3C insurance account.

The arbitration service is designed to establish insurance entity's trustworthiness and govern product quality that promotes fairness in the marketplace. In case the insurance entity fails to perform the risk transfer service within the set PORT timeframe, or the risk transfer service does not meet the description (i.e., poor quality, defective, inter-corrupted, etc.), the customer can open a dispute and auto-request a refund. The arbitration mechanism will engage participants of the blockchain via voting. A party at fault will be subjected to a penalty. The C3C tokens seized as a penalty will be withdrawn from circulation and “purge by deletion”.

The appeal process is designed to benefit the insurance entity, protecting from wrongful accusations and illegitimate claims brought forth by customers. The insurance entity can appeal, by submitting an (immutable) explanation and presenting digital-forensic evidence to the participants of the blockchain. If accused party is found not liable, the remaining party may be penalized.

The secure risk transfer feature may be a pay-for-use service. The rendering party may be responsible for paying a service fee in C3C tokens. The fee amount is determined by a vote by blockchain participants. C3C tokens collected as a payment for risk transfer may be removed from the blockchain via deletion.

Secure C3C Risk Transfer Algorithm

Listed are the algorithmic steps and risk attributes used to populate a C3C smart contract:Outline Smart Contract and policy terms of the “master” transaction, including risk transfer service timeframe and policy limits.All information may be registered in the blockchain through a distinctive hash generator.Using cryptocurrency wallet, a customer can review the product together with all financial and delivery terms and conditions.In case the customer decides to purchase the risk product/service, he/she must follow the transaction conditions outlined by the insurance entity.The funds payable to insurance entity may be held in escrow by system until the confirmation of risk transfer service is received from customer.In case the insurance entity failing to fulfill its risk transfer obligations, this may include poor quality of service and/or policy defects, risk limits, claim adjudication issues, etc., the customer can open a dispute, and (claim) request a refund.Once the policy dispute is opened, all participants of blockchain receive notification to join the arbitration process via smart-voting mechanism.Taking into account the amount of a refund, nature of the risk transfer service, and policy conditions, the automated arbitrage system may auto-calculate the timeframe and a number of blockchain participants to be involved as a jury to resolve a dispute.The platform may inform parties including blockchain participants about the number of time-cycles allocated for voting, and minimum votes needed to settle the dispute.Once the minimum number of votes has been reached within allocated timeframe, disputes may be settled to benefit customers.In case not enough votes are received, the disputed ticket may be closed.The party that does not prevail may be subjected to a penalty. The penalty may be calculated as a percentage of the amount being disputed.The C3C tokens collected as a penalty may be withdrawn from circulation, purged.Either party can appeal. An appeal fee may be charged to start the process. The appeal process may engage blockchain participants using voting mechanism.In case the appeal is lost by the appealing party, the collected appeal fee may be withdrawn from circulation and purged. The losing party pays penalty and costs of appeal.

Overall, the secure risk transfer feature is designed to benefit the customer and forces the insurance entity to fulfill their obligations. This system directly promotes better product quality, speedy cyber risk service, and the decentralized arbitration system may provide transparency to all disputes. In the long run, incorporating secure risk transfer feature in all financial insurance transactions will benefit the insurance entity by promoting honest business practices establishing trustworthiness and a good reputation.

The secure risk transfer service may function based on a more complex algorithm, making it fast, transparent and user-friendly. It is predicted that participants of cyber data insurance ecosystem will employ this service for all day-to-day online operations, as it will deliver a cyber-safety net for all B2C and B2B transactions. Further, it is predicted that the arbitration and appeal mechanisms may not be engaged often because participants in the data insurance system:will strive to conduct their business honestly, avoiding illegitimate transactions;work to build brand and trustworthiness in the cyber data risk marketplace;aspire to irradiate negative stigmas plaguing the cybersecurity industry;aim to comply with regulators and promote the regulation of cyber data insurance.

The C3C platform will enable the minimization of insurance fraud incidence and illicit activity in the digital marketplace, help to resolve disputes fairly with the use of blockchain and promote honest business practices and build strong B2B/B2C relationships. It is predicted that C3C features will stimulate cyber-related businesses to adopt the C3C as the main insurance transaction medium for all insurance operations.

CCL may utilize the utility-based CRT for its back-office operations at enterprise scale. Blockchain is not backed by any hard assets and no profit may be allocated to token holders by the Company. The C3C token is intended to be used within the CloudLedger platform and within further developed C3C platforms. C3C token holders may generate profit, because of their own entrepreneurial efforts on the secure risk transfer platform. C3Cs may run on decentralized “side-chain-based” blockchain, ensuring transparency and security of all financial transactions.

C3C CloudLedger Framework Components: The C3C CloudLedger blockchain framework is used to build enterprise blockchains for a consortium of software-defined, risk based solutions that are to roll-out over the following two years, which include CS identity, CS certification, CS compliance and data insurance. The C3C CloudLedger is different from public ledgers such as Ethereum. The C3C CloudLedger specifically in-sync accounts for the main-net “side-chain” transactions.

The CloudLedger components operate collectively with certain aspects of stability properties:Promise to offer service accuracy and stability based on PORTPromise to offer a service with a certain audit-based POSPromise to offer a certain service at a stated risk premium (pricing risk stability)Promise to encompass certain liability for risk transfer service fee (risk transfer guarantee)

The C3C CloudLedger framework includes:A decentralized “append only” distributed ledger;A consensus algorithm for agreement to change requests in the ledger;Privacy of transactions through ‘permissioned’ access only;Unique risk transfer properties that translate across multiple insurance services;Smart contracts to process “auto-enabled” transaction requests.

Upon completion of the STO generating C3C tokens, users will be able to:trade acquired C3C security tokens or convert into Ethereum, bitcoin and fiat currency via an ATS exchange;convert acquired C3C value into C3C utility risk tokens, or hold as a security investment;use C3C tokens to transfer or trade risk services within the ecosystem who require cyber risk insurance, or wish to purchase risk products offered by insurance partners;use C3C tokens to pay for risk membership services;use C3C tokens to pay for risk services offered by partners and risk products;use C3C token as a method of payment for premiums and services with participating broker/carriers of the cybersafety partner services.

Computer networks have come to be used for many aspects in business and personal life because computer networks enable large amounts of data to be accessed for a variety of purposes. There are increasing numbers of reported incidents concerning unauthorized access to information stored on computer networks. A variety of techniques have been developed in an effort to prevent the unauthorized access to information stored on computer networks.

In response, the persons attempting to obtain unauthorized access to information stored on computer networks have become increasingly more sophisticated in their efforts to circumvent the enhanced security methods. Most instances or attempts to obtain unauthorized access to a computer network come from outside of the company, because persons who have access to the computer network from inside of the company typically have undergone review prior to being provided with access to the computer network.

One technique to rate the potential risk of unauthorized access to the computer network is to selectively identify the cybersafety or cyber risk of a connection between the computer network and other computers, such as the internet, when it is desired to transmit and/or receive data. Using such a process significantly provides risk awareness because persons attempting to gain access to the computer network can determine not only when the connection is at risk near real time, but also verify the safety needed to access the network during a limited amount of time the connection is active.

With computer networks that are always connected to the internet, it is possible for unauthorized third-parties to periodically check the status of the connection to ensure that the connection is functioning prior to an unauthorized attempt to transmit data between the networks. The invention will apply blockchain-based resources to identify and account the IT event's network connection and determine permission-based access due to a smart-contract's protocol rules and policies that allow data at risk to move and transact. Risk transfer is embedded inline and real-time timestamped concerning the data's egress, thus enabling PORT.

The invention will enable offering the next generation of underwriting products, whereby our data lake shall enable insurance companies the ability to underwrite an enterprise's compliance risk for the first time-including data breach notification, property/liability insurance, blockchain insurance and the use of a customer's CS cyber-risk score history to set premium insurance limits. These unique, one-of-a-kind products will be the first risk-transfers products available in any market that exceed regulatory mandates.

Another embodiment of the invention is set forth inFIG.2.201is an on-premise dashboard that collects information relating to IT events on the customer site. The dashboard may show a variety of details such as geographic and real-time event priorities and risk scores.

202is an on-premise event uploader. In certain embodiments, the on-premise event uploader includes202aan event uploader for events, reading local real-time events. Data relating to these events may be packaged and sent to the CloudCover Cloud API. The on-premise event uploader may also include202ban event uploader for network events, reading local netflow events. Data relating to these events may be packaged and sent to the CloudCover Cloud API.

The next section, which is identified as Mississippi, may be utilized on an off-site data processing facility such as AWS Cloud Services. The section includes an event receiver203that hosts API services to receive data from all of the event uploaders relating that is sent from the on-premise devices202a,202b.

The events are extracted and restructured to be in time series clustered structure such as using a data transform process204. The processed data is then stored such as in time structured S3 storage205. Data from the Event API203is also processed to extract and restructure netflow events206, which also may be stored in the S3 storage205.

Next a computational complex time-aligning time-window based matching algorithm correlates207the event and the netflow events in a selected time period such as in 1 minute intervals. This process enriches the events with “in-bytes” and “out-bytes” for each event.

The enriched events are stored such as using S3 storage208prior to the next processing step. At209, a history of computation of events is stored such as in a DynamoDB, which enables continuous process. Finalized enriched events along with priorities, risk scores, risk rates are permanently stored in a database210such as DynamoDB. In certain embodiments, this data is stored for a period of time such as 3 days. Finalized enriched events are stored such as in S3 storage211.

Finalized enriched events are also sent to a dashboard212such as Kibana, which enables visualization of scores and rates. Status updater213periodically sends statistics from dashboard data to DynamoDB.

In the next section214, which is identified as Itasca, periodically retrieves event info. This data is consolidated and sent to a relay service such as Ethereum Relay Service to thereby sync to the Ethereum blockchain.

In the next section215, which is identified as Minnetonka, CloudCover smart contract receives events info, logs them as smart contract event logs, update policy status according to the scores and escrow states.

A captive office webapp (CloudCover Policy Manager) writes policy information securely into Ethereum Relay Service216. This relay service synchronizes the information to the Ethereum blockchain.

A captive office webapp (CloudCover Policy Manager) is hosted in AWS Cloud Services217that enables public access to create customer policies, monitor risk policies and manage policies for and with customers interaction, integration and approval.

The CloudCover mobile API services are hosted such as in AWS Cloud Services, serving mobile application functionality. The CloudCover mobile application, which include iOS and Android operating systems, interacts with CloudCover mobile API to aggregate all information from CloudCover including but not limited to (1) customer master policies, C3C blockchain events, real-time risk scores, risk rates, priority(s) and events(s) summary and alerts, notifications, etc.

Another embodiment of the invention is directed to a cybersafety origination tool, which is illustrated inFIG.3. The invention may be utilized in conjunction with a variety of mechanisms and configurations. In one such configuration, this embodiment of the invention is utilized in conjunction with virtual network.

As an initial aspect in using the cybersafety origination tool, an IT services menu300is provided. As used herein, IT means information technology. The IT services menu300may include a variety of options for a user to select. One of those options may include business policies310. After the business policies is selected, the user selects the data class312that is to be protected. Based upon the data class312that is selected, the user is presented with a data valuation class314to select. The user then selects InfoSec class316and micro services class318. Next, a notification class320and a data handling class322is selected.

The selected classifications are finished and recorded324. In certain embodiments, this recordation may be recorded in a blockchain. Utilizing the blockchain to record the classifications thereby protects this data.

Based upon the recorded classifications, a service recipe330is prepared. This service recipe330and a service component build332are used to prepare a service component lookup334.

The service recipe330then generates a service notification340that may be sent to the user. This service notification340may also be stored in a reports database342. In one such embodiment, the reports database342utilizes a blockchain in case there is a question as to the aspects of the service recipe330or whether the service notification340as sent.

The service notification340also engages CloudCover services350to initiate the process of providing cybersafety services to the user. Once the notification is received, the CloudCover services350records a CloudCover origination record352, which is then transferred to an actuarial record354. The actuarial record354also receives input from CloudCover validation from orchestration356. The actuarial record354is then sent to an underwriting system358. The CloudCover services350is also sent to the CloudCover transfer to orchestration module360.

In the preceding detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. In this regard, directional terminology, such as “top,” “bottom,” “front,” “back,” “leading,” “trailing,” etc., is used with reference to the orientation of the Figure(s) being described. Because components of embodiments can be positioned in a number of different orientations, the directional terminology is used for purposes of illustration and is in no way limiting. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. The preceding detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims.

It is contemplated that features disclosed in this application, as well as those described in the above applications incorporated by reference, can be mixed and matched to suit particular circumstances. Various other modifications and changes will be apparent to those of ordinary skill.