http:// is an insecure protocol running on port 80 that uses unencrypted traceable data for communication on uncertified, & unprotected websites. It is indicated that you are on one of these insecure websites by a warning, or lack of padlock in your web search URL.

An insider threat involves a trusted individual within the organization, such as a systems administrator, misusing their legitimate access to carry out malicious actions, like overwriting a supervisor's permissions.

Infrastructure as Code (IaC) allows security configurations, such as WAF policies, to be automatically provisioned and managed as part of the application deployment process, ensuring consistency and reducing manual effort.

Part 1

A firewall is placed at the edge to filter unwanted or malicious traffic from the Internet before it reaches internal resources.
A WAF specifically protects against web-based attacks like XSS, CSRF, and directory traversal by filtering and monitoring HTTP traffic.
A switch is used for internal network segmentation and connecting devices within the secure network.
The web server hosts the application and should be placed behind security controls for protection.
A PKI certificate enables HTTPS, ensuring encrypted and secure communication to mitigate insecure protocol risks.
Part 2

rsa:2048 - Generates a 2048-bit RSA key pair, providing modern, recommended key strength.
/certificate/example.com.csr - Saves the certificate-signing request that will be sent to a CA.
2048 bit long modulus - Confirms the key was generated with the intended 2048-bit length, validating the command sequence.

Enforcing 802.1X with device certificates ensures only authenticated devices can connect, and endpoint security checks verify compliance with security policies before granting network access, effectively mitigating unauthorized device risks.