trademark

4.0 Enpoint Input Validation/Filtering (cont.)
4.5 Secure the system against Sybil attacks
4.5.1 Why?
To detect and prevent one entity from masquerading as multiple identities in a system.
4.5.2 How?
• Trusted certificates (Section 4.1)
• Trusted devices (Section 4.7)
• Resource testing (Section 4.2)
4.6 Identify plausible ID spoofing attacks on the system
4.6.1 Why?
To detect and prevent an attacker from assuming legitimate identities.
4.6.2 How?
• Trusted certificates (Section 4.1)
• Trusted devices (Section 4.7)
• Resource testing (Section 4.2)
4.7 Employ trusted devices
4.7.1 Why?
To detect and prevent Sybil attacks and to prevent the compromise of endpoint devices
and applications running on them.
4.7.2 How?
Every entity in a system is assigned to an endpoint device with an embedded unique
device identifier, which is tied to a user identity in a 1-to-1 manner (e.g., a secure device
identity defined in IEEE 802.1AR). Then an attacker cannot create multiple identities
using a single device and the cost of acquiring multiple devices will be prohibitive.
CLOUD SECURITY ALLIANCE Big Data Working Group Guidance
© Copyright 2016, Cloud Security Alliance. All rights reserved.
24