spcl/serverless-benchmarks

Resource-specific permissions for functions

Open

#215 opened on Jul 27, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (99 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (196 stars)
PR merge metrics
 (PR metrics pending)

Description

Right now, our functions are created with permissions to access all needed resources, primarily the object storage buckets and in future key-value storage tables (PR #214)

Instead, we could make SeBS more secure with two additions: allocate permissions only to objects we allocate (e.g. by using prefix sebs-{resource_id} everywhere), and give each function only permissions associated with resources for that specific benchmark.

Contributor guide

Research direction
Investigate how to assign resource specific permissions using prefixes like 'sebs {resource id}' and modify the function creation code to restrict permissions per benchmark.
Tech stack
python
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Gitcloud computing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65