Coorpacademy
E-learning platform and content library for corporate training.
Education Technology · Europe
How Coorpacademy gets one view of its AWS account, spots what is no longer needed, and knows what to fix first.
Ten years of AWS, one evolving platform.
Coorpacademy, founded in 2013, runs its platform on an AWS account that has grown alongside the product for about ten years. Each new feature, integration and service adds permissions, and seeing how they all connect gets harder as the account grows. PanIAM complements the team's existing practices: it gives a clearer view of the account and makes continuous improvement easier.
The whole account, not brick by brick.
For Eric Sampaio, CTO of Coorpacademy by Go1, the first thing PanIAM changed was the view. In the AWS console, permissions are spread across users, roles and policies, and each screen shows what was granted directly, not where privilege escalation can take it from there. PanIAM draws the whole account as one map of who can reach what, escalation paths included.

Getting a global view of AWS is a bit complicated: you have to go brick by brick, and you don't see the links. It's all opaque. Here, you do get a view of the whole, and you can follow the path.
How permissions connect, made visible.
Any account that has grown for a decade carries permissions granted for needs that have since evolved. The console shows them one at a time, so the links between them are hard to follow. PanIAM's map made those links visible, including access that reached further than expected.

PanIAM's graphical view helped us better understand the links between permissions, and showed access rights that were sometimes broader than we imagined.
Spotting what is no longer needed.
PanIAM also makes it easier to identify permissions and resources that are no longer needed. After the first analysis, the team removed the ones that had outlived their purpose.

It also helped me identify things that were deprecated, so we could remove them. We don't necessarily all have the reflex to say: we don't use this anymore, so let's clean it up. We tend to accumulate, and this makes you realize: what is this thing? Then you follow the branch down and say: actually, no, it isn't used, so we can delete it.
Clear next steps, in order of priority.
Every finding comes with a concrete fix, ranked by the resources it protects, so the team knows what to address first. Applying the first four lowers the account's PanIAM risk score by 49.3%. For Eric, this is where PanIAM makes the difference: beyond detection, clear next steps to move forward.

Detecting is good, but I think proposing solutions to fix things brings even more.
From a one-off audit to continuous improvement.
PanIAM's weekly email shows what has changed in the account, what to fix first and whether past fixes made a difference. It turns a one-off review into a regular routine, and gives Eric a measure of progress he can share, investors included.

I see two phases. First the audit: you run it once, get recommendations and fix. Then come day-to-day operations.
Ready to see your whole account at once?
Connect it to PanIAM to map who can reach what, and spot what is no longer needed.
