Securing Terraform and You, Part 3 -- The Finish Line

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

I swear, this is not a recurring series. The problem just -- finally -- got solved. Part 2 is over here.

I went back to tfsec after seeing the simple start guide posted here, by Liam Galvin at Ghost Security.

There are two aspects of my code:

Allow buckets starting with [word]
deny buckets that don't start with [word].

The initial guide only has "don't allow buckets that are exactly named this", but that's all I needed to actually get going!

The problems could have been;

The rego file and the terraform file don't play well in the same folder. Having the options in two separate subfolders helped even though there was a command that I used to read both files in the same folder.
Trivy ... I don't know. Maybe the metadata setup was incorrect - but if it's set up as comments -- readable by the program but not acknowledged in the rego -- who knows. I can work on that in the future.
The code was similar though not exact to examples and code I puzzled together initially. 100% it could be wrong (also, ChatGPT didn't know how to write it either. Is this too new and the ChatGPT learning model doesn't know it? )

Remember - tfsec has been bought by Aqua Security, the people behind Trivy; This code could probably work if I put in the correct metadata tags and use the right command.

You went back and forth between two programs (tfsec and Trivy) - Why did you stick with coding this solution in rego instead of another language that was compatible with the software?

I'm writing this in Feb of 2024; Probably sunk cost fallacy and feeling that rego, even with its difficulty, was easier to read as code for me than Python is.

Comments

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

If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return. 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

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

RUN TCP/IP | Morgan Lucas is Tech Blogging

Search This Blog