Zilvinas Saltys
Zilvinas Saltys
There was recently a fix for 2.3 related to how GET_ORGANIZATION permission works: https://github.com/data-dot-all/dataall/pull/1139 The summary of the issue is that if you are a member of an environment team...
We've ran into multiple situations where our users delete a role which is actively used in data.all. We can detect this (with custom scripts) and data.all will let you revoke...
There are various policies installed by data.all granting unrestricted access to resources. This gets picked up by Checkov security scanner. By unrestricted I mean **granting actions on resource '*'**. This...
Currently all graphql endpoints respond with header: Access-Control-Allow-Origin: *. This allows to make calls from other origins outside data.all domain. In reality this is very low or non existent security...
### Describe the bug After we installed data.all 2.3 we noticed that we cannot view any team permissions in Admin console and were getting a JS error. This is because...
Node.js v16 runtime is scheduled to be deprecated Jun 12, 2024. Therefore we should upgrade all lambdas to Node.js 20 runtime.
The pivot role installed on AWS accounts has policies which are picked up by Checkov scanner where the role has unrestricted access. By unrestricted I mean **granting actions on resource...
AWS DataZone has a feature called: **Metadata Forms**. Essentially it's a dynamic form creator that can be attached to datasets. I think this is an excellent feature and it would...
Currently environment team invite page uses a different react component than the rest of the pages like environment linking and it allows to type any team name even if it...
Currently the github action is using checkov to scan data.all repo. However it cannot find much because most of the stacks are generated with CDK. We should generate the stacks...