LambdaGuard

AWS Serverless Security

AWS Open Source Self Hosted Only
Category Serverless Security
Community Stars 400
Last Commit 4 years ago
Last page update 19 days ago
Pricing Details Free and open-source
Target Audience AWS developers and security professionals.

LambdaGuard addresses the critical security and visibility gaps in AWS Lambda environments by providing a comprehensive auditing tool. The core challenge it tackles is the lack of transparency and control over serverless functions, which can lead to unnoticed security vulnerabilities and misconfigurations.

Technically, LambdaGuard is built using Python and optionally integrates with Java for SonarQube static code analysis. It requires AWS access keys and permissions to scan Lambda functions, which can be configured via a profile in the ~/.aws/credentials file or passed as CLI arguments. The tool performs statistical analysis, checks AWS service dependencies, and conducts configuration audits from a security perspective. This is achieved through commands like lambdaguard --function arn:aws:lambda:function and lambdaguard --input function-arns.txt, allowing for both individual function and bulk audits.

Operationally, LambdaGuard is relatively straightforward to set up, with installation options via PyPI or a GitHub clone. However, it does require careful management of AWS credentials and permissions to ensure proper access without compromising security. The integration with SonarQube adds an additional layer of static code analysis, which can be configured using a JSON file specifying the SonarQube URL, login, and password.

Key operational considerations include the need for consistent credential management and the potential overhead of running SonarQube for static code analysis. While LambdaGuard provides detailed outputs, the volume of data can be significant, especially in large-scale Lambda deployments, which may impact storage and processing resources. Additionally, the tool's performance and scalability depend on the efficiency of the underlying AWS API calls and the configuration of the auditing process.

Improve this page