The scenario describes a decentralized cryptographic trust model where each user maintains a ring or database of public keys, and communications are encrypted using the recipient's public key. This aligns precisely with the Web of Trust (WOT) model.
According to the CEH v13 Official Courseware:
* Web of Trust (WOT) is a decentralized trust model used primarily in PGP (Pretty Good Privacy) environments.
* In WOT:
* Each user maintains a local keyring of trusted public keys.
* There is no central Certificate Authority (CA).
* Trust is built based on mutual verification and endorsement of public keys among users.
* It uses asymmetric cryptography: messages are encrypted using the receiver's public key and decrypted using the corresponding private key.
* This model provides authentication (via digital signatures) and message integrity (via cryptographic hash functions).
Incorrect Options:
* A. Zero Trust Network is a security architecture that enforces strict access control but is not a cryptographic trust model.
* B. TLS (Transport Layer Security) is a protocol for securing data in transit, commonly used in HTTPS, and relies on the PKI trust model (not WOT).
* C. SSL (Secure Socket Layer) is an outdated version of TLS, also based on centralized certificate authorities.
Reference - CEH v13 Official Courseware:
* Module 20: Cryptography
* Section: "Public Key Infrastructure (PKI) and Trust Models"
* Subsection: "Web of Trust (WOT) Model"
* Study Guide Table: Comparison of Trust Models - PKI vs WOT vs Hybrid
Lab references in CEH Engage may also cover key signing and verifying concepts in decentralized environments.

This falls under Requirement 8 of PCI DSS: "Identify and authenticate access to system components," which supports the objective of implementing strong access control measures.
CEH v13 Reference:
Module 20: Hacking Mobile Platforms and IoT - Compliance Standards
"PCI DSS requires unique identification for each person with access to ensure accountability and access control."

The File Transfer Protocol (FTP) is a standard organization convention utilized for the exchange of PC records from a worker to a customer on a PC organization. FTP is based on a customer worker model engineering utilizing separate control and information associations between the customer and the server.[1] FTP clients may validate themselves with an unmistakable book sign-in convention, ordinarily as a username and secret key, however can interface namelessly if the worker is designed to permit it. For secure transmission that ensures the username and secret phrase, and scrambles the substance, FTP is frequently made sure about with SSL/TLS (FTPS) or supplanted with SSH File Transfer Protocol (SFTP).
The primary FTP customer applications were order line programs created prior to working frameworks had graphical UIs, are as yet dispatched with most Windows, Unix, and Linux working systems.[2][3] Many FTP customers and mechanization utilities have since been created for working areas, workers, cell phones, and equipment, and FTP has been fused into profitability applications, for example, HTML editors.

A cloud carrier acts as an intermediary that provides connectivity and transport of cloud services between cloud consumers and cloud providers.
Cloud carriers provide access to consumers through network, telecommunication and other access devices. for instance, cloud consumers will obtain cloud services through network access devices, like computers, laptops, mobile phones, mobile web devices (MIDs), etc.
The distribution of cloud services is often provided by network and telecommunication carriers or a transport agent, wherever a transport agent refers to a business organization that provides physical transport of storage media like high-capacity hard drives.
Note that a cloud provider can started SLAs with a cloud carrier to provide services consistent with the level of SLAs offered to cloud consumers, and will require the cloud carrier to provide dedicated and secure connections between cloud consumers and cloud providers.

In CEH v13 Module 16: Cloud Computing and Container Security, Cloudborne attacks are described as threats specific to bare-metal cloud infrastructure.
Characteristics of a Cloudborne Attack:
Targets firmware-level vulnerabilities in reused physical servers.
Malware or backdoors can persist even after VM or OS reinstallation.
Can lead to compromise of new tenants or clients once servers are reallocated.
First highlighted in Project X by Eclypsium.
Option Clarification:
A: MITC: Exploits synchronization in cloud storage, not firmware.
B: Cryptojacking: Mining cryptocurrency using cloud resources.
C: Cloudborne attack: Correct - targets firmware on bare-metal cloud servers.
D: Metadata spoofing: Exploits cloud instance metadata services, unrelated to firmware.
Reference:
Module 16 - Advanced Cloud Attacks # Cloudborne Threats
CEH eBook: Firmware-Level Threats in Cloud Environments