# Link-Layer Encryption

Link-layer encryption protects data frames between network peers at Layer 2, securing a link or segment rather than an entire application-to-application path.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/link-layer-encryption

> Link-layer encryption provides confidentiality and, with protocols such as MACsec, integrity and data-origin authentication for traffic crossing a network link. It matters in hybrid and multi-cloud connectivity because a private circuit is not automatically encrypted, and protection ends wherever the encrypted link terminates.

Practice exams covering Link-Layer Encryption: [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty).

## 6 key aspects of Link-Layer Encryption

Effective link-layer encryption depends on clearly defined endpoints, compatible infrastructure, managed keys, and verified behavior during failures and failover.

1. **Explicit protection boundaries**: Encryption covers the path between participating link-layer peers, not automatically the full route to a workload. Document the termination points and assess every segment outside that boundary.
2. **Confidentiality and frame integrity**: MACsec can encrypt frame contents and detect unauthorized modification, with replay protection configured at the receiver. It does not conceal all Ethernet metadata or replace routing and access-control policies.
3. **Independence from private routing**: A dedicated circuit, VLAN, or private IP route does not itself provide encryption. Verify encryption support and configuration separately from the connectivity service.
4. **Hardware and transport compatibility**: Both endpoints must support compatible encryption capabilities, and intervening transport must carry the required traffic. Confirm cloud connection eligibility, device support, and frame-size handling before deployment.
5. **Key management and failure policy**: Coordinate peer credentials, key identifiers, and rotation procedures. When encryption is mandatory, configure and test a policy that blocks traffic rather than allowing unencrypted fallback.
6. **Complementary encryption layers**: Use IPsec when protection must span routed networks and TLS when protection must extend between application-facing endpoints. Multiple encryption layers can be appropriate when they address different trust boundaries.

## Cloud services for Link-Layer Encryption

AWS Direct Connect, Azure ExpressRoute Direct, and eligible Google Cloud Dedicated Interconnect connections can use MACsec to protect their respective access links. In a hybrid or multi-cloud architecture, configure and validate each link independently because one provider's encrypted connection does not secure another provider's connection or the intervening enterprise network. AWS Site-to-Site VPN adds IPsec protection between VPN endpoints when that boundary better matches the requirement. Application TLS can remain necessary regardless of the connectivity choice. Select the layers by mapping trust boundaries, then verify that primary and backup paths satisfy the same encryption policy.

- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Supports MACsec on eligible dedicated connections at supported locations, protecting the link between compatible customer equipment and the AWS Direct Connect device. Private connectivity is not encrypted by default, and MACsec does not by itself provide end-to-end encryption to workloads.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: Provides IPsec encryption at the network layer, not MACsec or other link-layer encryption. It complements or provides an alternative to access-link encryption when the required protection boundary is between VPN endpoints; running it over Direct Connect requires a supported connectivity design.

## Link-Layer Encryption exam questions

Real practice exam questions on Link-Layer Encryption, with the correct answer and its explanation.

### Question 1 (SCS-C03)

**Question:**

A financial company replicates transaction records from an on-premises application to an application running on Amazon EC2. Traffic uses a dedicated AWS Direct Connect connection with MACsec enabled between the company's edge router and the Direct Connect device. The replication protocol currently sends records in plaintext.

An audit requires cryptographic protection continuously from the on-premises application process to the EC2 application process. Network devices and intermediate services must not have access to plaintext records. The company can change application connection settings but must retain the existing network path.

Which change meets these requirements?

**Correct answer:** Configure the replication client to use TLS directly to the EC2 application, validate the server certificate's trust chain and hostname, and require encrypted connections on the application listener.

**Explanation:** TLS established directly between the replication client and the EC2 application protects records across the entire required path without exposing plaintext to intermediate network devices or services. Certificate validation authenticates the intended server, and requiring encrypted connections prevents plaintext fallback.

## Practice Link-Layer Encryption in a full exam

Questions on Link-Layer Encryption in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 4 questions

## What is Link-Layer Encryption

Link-layer encryption protects traffic at the data-link layer of the network stack. Instead of establishing an encrypted session between applications, it protects frames exchanged between participating network devices. IEEE 802.1AE MAC Security, commonly called MACsec, is an important implementation for Ethernet connectivity. MACsec can provide confidentiality, integrity, data-origin authentication, and replay protection for protected frames, while leaving information needed for Ethernet forwarding visible.

The most important design question is where encryption begins and ends. A MACsec session might extend between an enterprise router and a cloud provider's edge device. Traffic is decrypted at the receiving MACsec endpoint; that session does not establish continuous encryption through the cloud network to a virtual machine or application. Additional controls may protect later segments, but engineers must assess those segments separately rather than infer end-to-end protection from an encrypted access link.

In hybrid architectures, link-layer encryption is useful when workloads need high-throughput private connectivity and the organization must protect traffic on the access circuit. AWS Direct Connect supports MACsec on eligible dedicated connections at supported locations. Both the customer equipment and the selected connection must support the required MACsec capabilities. A Direct Connect connection is not encrypted by default, and MACsec availability must not be assumed for every connection type, port speed, or location.

For example, an enterprise connecting a data center to AWS can enable MACsec between its compatible router and the Direct Connect device. If a carrier supplies a transport segment between those endpoints, engineers must confirm that it transparently carries the required frames and supports the intended design. They must also identify any network segment before the customer router that remains outside the MACsec protection boundary. In a multi-cloud deployment, each provider-facing connection needs its own capability assessment and protection plan.

MACsec, IPsec, and TLS solve different problems. MACsec protects a Layer 2 link or segment. IPsec protects IP traffic between tunnel endpoints and can span routed networks. TLS protects traffic between TLS endpoints, which may be applications or intermediary proxies. AWS Site-to-Site VPN uses IPsec rather than link-layer encryption. It can complement private connectivity when the required encrypted boundary extends beyond the physical access link, but its supported routing architecture, throughput, tunnel overhead, and MTU implications must be evaluated.

Link-layer encryption can often operate at port line rate using hardware support, avoiding the throughput limitations of some software-based encryption designs. Its trade-offs include compatible equipment, eligible cloud ports, frame overhead, key management, and operational complexity. With MACsec Key Agreement, peers establish secure associations using configured credentials; engineers must coordinate parameters and rotate keys without unexpectedly interrupting connectivity.

Troubleshooting should distinguish physical connectivity, encryption negotiation, and routing. An interface can have carrier while MACsec negotiation fails, and a working encrypted session does not prove that BGP or application traffic is healthy. Check peer capabilities, key identifiers, configured keys, cipher compatibility, security policies, and frame counters. Decide explicitly whether loss of encryption must stop traffic: a policy that permits unencrypted fallback can preserve availability while violating a mandatory encryption requirement. Test failover links as well, because a backup path can otherwise silently weaken the security design.

## Learn Link-Layer Encryption in lessons

1 short lesson on Link-Layer Encryption in 1 certification course.

- SCS-C03: Link-Layer Encryption: MACsec on hybrid access links (Premium), https://app.blowstack.com/lessons/link-layer-encryption-macsec-on-hybrid-access-links-scs-c03
