getting adom to work in fortiweb

[robinmordasiewicz]

Aims to enable the integration of ADOM (Administrative Domain) functionality in FortiWeb within the FortiWeb configuration files. By adding the necessary configurations in the terraform/cloud-init/fortiweb.conf file, we are ensuring that the ADOM administration is enabled and the system settings are appropriately configured to support ADOM functionality.

Additionally, the modifications in the configuration settings include enabling OWASP Top 10 compliance, setting up file upload capability, configuring dashboard widgets for improved visualization, and enhancing system security features such as traffic logging and disk management.

These changes enhance the overall functionality and security posture of the FortiWeb deployment within the FortiWeb configuration files, aligning it with best practices and ensuring a more robust and secure deployment.

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ COPYPASTE	jscpd	yes		no	1.39s
✅ JSON	jsonlint	1		0	0.34s
✅ JSON	prettier	1	0	0	0.56s
✅ JSON	v8r	1		0	1.72s
✅ REPOSITORY	checkov	yes		no	19.54s
✅ REPOSITORY	dustilock	yes		no	1.38s
❌ REPOSITORY	gitleaks	yes		1	24.06s
✅ REPOSITORY	git_diff	yes		no	0.13s
✅ REPOSITORY	grype	yes		no	21.47s
❌ REPOSITORY	kics	yes		28	65.42s
✅ REPOSITORY	secretlint	yes		no	1.41s
✅ REPOSITORY	syft	yes		no	0.46s
✅ REPOSITORY	trivy	yes		no	11.14s
✅ REPOSITORY	trivy-sbom	yes		no	3.64s
✅ REPOSITORY	trufflehog	yes		no	4.31s
✅ TERRAFORM	terraform-fmt	3	0	0	0.36s
❌ TERRAFORM	terrascan	yes		1	7.36s
✅ TERRAFORM	tflint	yes		no	3.09s
✅ YAML	prettier	1	0	0	0.55s
✅ YAML	v8r	1		0	2.13s
✅ YAML	yamllint	1		0	0.72s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by