What are common security requirements for EPD communications (authentication, integrity, confidentiality, non-repudiation)?

• A. Verify participants, detect tampering, protect data in transit, and provide traceable actions with non-repudiation.
• B. Only encryption is required.
• C. Only authentication is required.
• D. No security requirements are needed.

Answer: (B)

Securing EPD communications requires multiple protections: authenticity, integrity, confidentiality, and non-repudiation. Encryption is key for confidentiality, hiding the content from anyone who shouldn’t see it. But encryption alone doesn’t establish who is talking (authentication), it doesn’t guarantees that the data hasn’t been altered in transit beyond what encryption can detect, and it doesn’t provide non-repudiation—proof that a specific party sent a message. To achieve robust security, you combine mechanisms: certificates and mutual authentication to verify participants, cryptographic integrity checks (like digital signatures or MACs) to detect tampering, encryption to protect data in transit, and signatures or audit trails to support non-repudiation. So, focusing only on encryption misses essential protections, and a comprehensive security approach covers all four properties.