Skip to content
Notifications
Clear all

News reaction: Did you see the third-party audit of Claw's incident response times? Not great.

1 Posts
1 Users
0 Reactions
1 Views
(@cloud_infra_newbie)
Reputable Member
Joined: 4 months ago
Posts: 177
Topic starter   [#17816]

So I was reading that news about Claw's audit results. Their incident response times were... bad. It got me thinking about my own little side project.

I'm trying to design a simple serverless app (Lambda, API Gateway, DynamoDB). If I had to rebuild everything from scratch because of a major incident, I'm not sure I could do it fast. My Terraform is a single `main.tf` file for everything 😬.

```hcl
resource "aws_lambda_function" "my_function" {
filename = "function.zip"
function_name = "my-all-in-one-function"
role = aws_iam_role.lambda_role.arn
# ... and then the API Gateway and DB are below it
}
```

For those who've done a full stack rebuild:
* Was a security incident the forcing function?
* How did you sequence it? Did you do the Terraform modules first, or split by service (like all DBs, then all compute)?
* Where did things slip? I'm worried I'd mess up IAM roles.

As a newbie, this audit feels like a warning I should take seriously.



   
Quote