5. IPv6 Global Unique Address

IPv6 global Unique address (GUA) is a type of IPv6 address that is routable over the Internet, allowing devices to communicate globally. This section will explore the process by which GUAs are allocated to enterprises and service providers, including the roles of key organizations like IANA, RIRs, and LIRs. We will also cover how addresses are ultimately assigned to individual endpoints.

Details

4. IPv6 Link Local Address

An IPv6 link-local address with the prefix FE80::/10 is a IP address that is automatically or manually assigned to an IPv6-enabled device for local network (link) connectivity. These addresses are always present on an IPv6 interface, even if other address types are assigned. They play a critical role in IPv6 networks, supporting essential functions like neighbor discovery, automatic address configuration, and local communication, which are vital for the proper operation of an IPv6 network.

Details

2. Compare IPv4 and IPv6 Headers

This lesson focuses on the differences between IPv4 and IPv6 headers. We will explore which IPv4 header fields have been removed in IPv6, what new fields and capabilities have been added, and which fields have been renamed. Additionally, we will discuss how the experiences learned from IPv4 have contributed to the development of a more efficient IPv6 header.

Details

27. F5 AWAF Parent Policy

F5 AWAF parent policy serves as a baseline security template from which individual web application security policies can inherit. This approach ensures consistency across all applications, reduces the administrative overhead associated with creating and updating policies, improves overall security by applying uniform and up-to-date security measures, and enhances scalability in managing application security.
In this section, we will discuss and demonstrate the benefits and implementation of the F5 AWAF parent policy.

Details

26. F5 AWAF Logging

This section will cover the logging capabilities of F5 AWAF, including remote logging to capture security events on a remote server, response logging to track web application response traffic, and content events logging, which ensures that application security events are logged in “/var/log/asm”. These logging features are essential for effective security monitoring and incident response.

Details