Skip to main content

Securing Terraform and You Part 2 -- Trivy by AquaSecurity

9/20: The open source version of Terraform is now OpenTofu 


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


the homebrew package had an outdated version, so I had to install v. 0.40.0 myself and link it to the previously installed 0.18.0 I believe -- See the GitHub discussion here.

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 (Department?) Trivy scans has it's own folder, most empty.

the only policies in place (I could not find the secret YAML file) is about Remote Desktop Services. 

the metadata is in JSON, and is commented out, though it does provide a rego example!

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. 

As of this posting, I still haven't figured it out. The code looks right to me, to others. Good news, on August 11th, the problem was solved [Click here]!


OPA/rego may be easy to use and learn, but I haven'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. 

Open Policy Agent / rego may be flexible, but the learning curve is steep and not accessible to quickly getting up to speed.

To conceptualize or test something, an employer would want a quick solution.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory