Geoff
|
4961498562
|
Added parameter to report resource name
Added a third parameter to checks textFail and textPass to identify resource name in finding.
|
2021-06-16 22:25:44 -05:00 |
|
Toni de la Fuente
|
a9d56be81a
|
Added risk, remediation, doc link and caf epic to checks 742 to 7133
|
2021-03-24 15:12:32 +01:00 |
|
Toni de la Fuente
|
f85845c26b
|
Added service name to all checks
|
2021-01-22 00:19:45 +01:00 |
|
Joaquin Rinaudo
|
ecbe997084
|
severity+security_hub
|
2020-09-03 08:04:13 +02:00 |
|
Toni de la Fuente
|
7f03ef0e7e
|
Adding back extra798
|
2020-08-27 16:50:48 +02:00 |
|
Toni de la Fuente
|
36a291c4a9
|
Rename check_extra798 to check_extra7100
|
2020-08-27 16:30:20 +02:00 |
|
Toni de la Fuente
|
0b9d3e39d4
|
Merge branch 'master' into master
|
2020-08-27 16:28:35 +02:00 |
|
Toni de la Fuente
|
565edf7b4b
|
Change check ID to extra7100
Change check ID to extra7100
|
2020-08-27 16:21:56 +02:00 |
|
Toni de la Fuente
|
ca471700c2
|
Added [extra798] Check if Lambda functions have resource-based policy set as Public
|
2020-08-25 19:06:06 +02:00 |
|
Nick Malcolm
|
ba87f437d5
|
This check will identify IAM Policies which allow an IAM Principal (a Role or User) to escalate their privileges due to insecure STS permissions. It is AWS best practice to only use explicitly defined Resources (Role ARNs) for an sts:AssumeRole action.
See more: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_permissions-to-switch.html#roles-usingrole-createpolicy
|
2020-08-20 21:08:00 +12:00 |
|