Sourceless / Sourceless/infratomic

Epic: Auto-remediate governance bypass and IaC drift via Terraform

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
0
Forks
0
Avg merge
12m
Merged PRs (30d)
3

Description

TL;DR: Detect unmanaged/drifted AWS resources on a schedule and reconcile them by running Terraform itself, so policy violations (like an open port 22) don't stay live between manual syncs.

User story

As a security engineer, I want out-of-band changes and config drift auto-detected and reverted, so governance bypasses don't sit unresolved until someone notices.

Acceptance criteria

  • Sync runs automatically on a schedule
  • Attribute-level drift on managed resources is detected
  • Backend can run terraform apply/import/destroy unattended
  • Policy-violating resources are auto-reconciled via Terraform, not direct AWS API calls

How to verify

Hand-create a security group rule opening port 22 to 0.0.0.0/0 directly via AWS API (bypassing Terraform). Wait one scheduled cycle. Confirm it's destroyed with no human action.

Out of scope

  • Direct AWS API mutation (e.g. RevokeSecurityGroupIngress) — remediation always goes through Terraform

Sub-tickets

  • #31 Run Sync automatically on a schedule
  • #32 Detect attribute-level drift on managed resources
  • #33 Add unattended terraform apply/import/destroy execution
  • #34 Auto-reconcile policy violations via Terraform

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading sub-tickets #31–#34, then use the acceptance criteria and the port-22 verification scenario to understand the required behavior. Done means scheduled drift detection reconciles violations through unattended Terraform operations, without direct AWS API mutation.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, terraform
Domain
cloud, infrastructure, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.