Image Credit: Pixabay on Pexels
Securing Terraform and You, Part 2
By Morgan Lucas
This is a post intended for this site, as a way to get a feel of using it consistently. Older posts are here.
This comes as the 3rd tool in a long line of tools I am using to make Terraform (OpenTofu) code consistent. I went back to the Styra Academy courses for OPA Policy Writing. I am a very "Just show me the general idea, and I can probably figure it out", and I am reasonable enough to say that it didn't work this time, and I had to take the slow road.
Good start; Trivy told us where it installed;
trivy info installed /usr/local/bin/trivy
/Users/morganza/Library/Caches/trivy
The homebrew package had an outdated version, so I installed v. 0.40.0 myself and link it to the previously installed 0.18.0 I believe -- See the GitHub discussion here.
Using rego (pronounced ray-go)
We are now back to rego, but fortunately, Trivy works as intended when you run it locally with the following command;
trivy conf --policy . --namespaces morganza .
There was an odd combination of YAML with a bit of rego involved for tfsec -- can we do that here?
It got to the point where I had to dig around in the config files for an example. It's quite organized, and every section of a cloud network Trivy scans has it's own folder, most empty.
The only policies in place (I could not find the secret YAML file) are about Remote Desktop Services.
the metadata is in JSON, and is commented out, though it does provide a rego example!
Back and Forth
I had to go back and forth between the rego GitHub and the Trivy GitHub; People know either one or the other, not both.
If you need to set up some rules once and edit them very rarely, using rego will be great. If you plan to use it a lot, you will get a lot of practice and be good at it.
Open Policy Agent/rego may be easy to use and learn, but I hadn't found the solution -- or someone who can walk me through to it -- yet. If Trivy allowed us to write policies in more popular languages, it would be a good start.
But head on to part 3 to see how I solved it.