https://fortinetcloudcse.github.io/faig-training-workshop/index.htmlIntroduction to the FortiAIGate product.Hugoen-UShttps://fortinetcloudcse.github.io/faig-training-workshop/01_environment_setup/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/faig-training-workshop/01_environment_setup/index.htmlInitial Environment This lab requires you have a working Kubernetes (K8s) environment in Azure. We will be using helm via the Azure Cloud Console to setup the existing nodes and pods that we will use during this session. Complete Previous Labs First This lab requires you to have completed the following sections from the “k8s01-101-workshop”: Workshop Logistics: Task 1 - Setup Azure Cloud Shell - This ensures that you have properly setup the Cloud Console and have access that you will need in the next sections. Workshop Logistics: Task 2 - Run Terraform - This task will ensure that you have a working set of VMs to use as your K8s cluster. This sets up the VMs in Azure via Terraform and ensures that they are ready for the next section. Self Managed K8s Workshop: Task 1 - K8s Installation - This will install K8s on the VMs for you and make sure that you have all the software required to complete the following sections. Confirming the Environment Let’s confirm that the environment is setup correctly and has everything we need before we get started. If any of these checks fail, please go back and confirm that you have completed the sections listed above in “Complete Previous Labs First”.https://fortinetcloudcse.github.io/faig-training-workshop/02_fortiaigate_setup/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/faig-training-workshop/02_fortiaigate_setup/index.htmlFortiAIGate Installation In the previous sections we worked on getting an environment to run Kubernetes (K8s), installing K8s, and setting up additional containers and pods to build out the resources we will protect in this demo environment. The next step will be to install FortiAIGate itself using the supplied helm charts that come with the FortiAIGate release files. Background Information FortiAIGate is distributed via a collection of container files in tar (Tape ARchive) format that must be loaded into a container repository so that they are available for download by K8s when deployed. We have already completed this step for you, but a customer might need to setup their own repo server (for example the Harbor repository server) and upload the images there. The FortiAIGate values.yaml file would need to be updated to reflect that new repo server location.https://fortinetcloudcse.github.io/faig-training-workshop/03_fortiaigate_config/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/faig-training-workshop/03_fortiaigate_config/index.htmlAccessing FortiAIGate and Initial Setup We will need to access the FortiAIGate to make some initial changes and grab some required information to help us setup the environment. Logging In to the FortiAIGate Log into the Azure Portal. Open the Azure Cloud Console. Run the following command so that we generate the URL to access the landing page.https://fortinetcloudcse.github.io/faig-training-workshop/04_demo_fortiaigate/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/faig-training-workshop/04_demo_fortiaigate/index.htmlDemoing the FortiAIGate In this section we will show how the FortiAIGate enforces, monitors, and protects LLM communications for customers. We will show the process using a three step process: Expose - demonstrate the vulnerability on an unprotected LLM with real attack payloads Configure - apply the FortiAIGate control (AI Guard scanner + action) Validate - confirm the action with the same payload, view logs, and occasionally run a negative test to verify existing operations Each phase will produce log evidence (subtype=ai-security, action=blocked) suitable for compliance audits and security posture reporting.