You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: