dashboard threat model #67
Conversation
|
|
||
| | Term | Definition | | ||
| | --------------------- | ----------------------------- | | ||
| | mTLS | Mutual Transport Layer Security (mTLS) allows two parties to authenticate each other during the initial connection of an SSL/TLS handshake. | |
There was a problem hiding this comment.
Is there any mention of mTLS in this doc? Feels like it might be a copy-paste.
|
|
||
|  | ||
|
|
||
| Given that the Radius Dashboard is developed as a Backstage plugin, it is essential to first examine the Backstage architecture. Backstage provides a core Single Page Application (SPA), a core backend, and the ability to configure a desired database. The core functionality can be enhanced using plugins. |
There was a problem hiding this comment.
Can you clean this up? See above ^^^
|
|
||
| 1. Dashboard should be accessed only on HTTPS if it should be available outside cluster. Currently, we can access the application on http but since we only access the application on localhost using =kubernetes port-forward, this is OK. | ||
|
|
||
| 2. Enable authentication on Dashboard. This could be tied to RBAC support on Radius, since we might want the same users to be allowed dashboard logins by default with permissions configured using Backstage permission system. |
There was a problem hiding this comment.
What's the actual action item? Is this something the user needs to do? If that's the case what's the action item for us?
There was a problem hiding this comment.
Add documentation in dashboard related info to capture this.
|
|
||
| Due to the volume of requests Dashboard as well as the UCP, AppCore-RP components involved in serving the request could run out of resource to serve a legitimate request. | ||
|
|
||
| **Mitigation**: |
There was a problem hiding this comment.
Have we explored an option to configure rate limiting?
There was a problem hiding this comment.
we discussed this in meeting and how we can use permission system to make sure we dont get too many requests (which would be from unauthorized users)
| #### Threat 3: Spoofing dashboard service-account can cause DoS | ||
| **Description** | ||
|
|
||
| If an unauthorized user or malicious actor gtampers with cluster, |
There was a problem hiding this comment.
nit: typo
| If an unauthorized user or malicious actor gtampers with cluster, | |
| If an unauthorized user or malicious actor tampers with cluster, |
|
add info on radius rbac and its impact on backstage/dashboard |
|
|
||
| ## System Description | ||
|
|
||
| The Dashboard component is an instance of [Backstage](https://backstage.io/). We customize Backstage by installing a Radius plugin and the community-supported Kubernetes plugin. The Dashboard is a client of the Radius API. It queries the graph of an application or a list of environment and constructs a visual representation of the response. |
There was a problem hiding this comment.
This is very clear now, thank you 🙏
Signed-off-by: nithyatsu <[email protected]>
Signed-off-by: nithyatsu <[email protected]>
Signed-off-by: nithyatsu <[email protected]>
Add threat model for Radius dashboard