Feature Requests

We need to have an expiration date feature for API keys. This is essential to enhance security by ensuring that API keys are automatically deactivated after a specified period, thereby significantly reducing the risk of misusage.

As a Platform admin, I would like to create tags and policies at a Platform level in order to set up customized behaviour on my own, without affecting other Platforms. As an example, I want to apply some tags and policies in the LZs of my Platform to scope the usage of services (Building Blocks) in them. I want to be able to make frequent changes in those tags and policies in a day-to-day basis. Right now, administrators of the Platform are not currently provided any option to deploy those changes, and must align them with other Platform teams, losing flexibility and efficiency.

Duplicate tag entry is currently required when the same tag information, such as Environment designations (Production, QA, Test), needs to be applied to different meshstack objects like LandingZone and Project. This manual redundancy is inefficient and creates opportunities for errors in data entry.

Currently, we set up custom Azure RBAC Roles for Azure landing zones. In order to prevent privilege escalation, the Microsoft.Authorization/roleAssignments/write permission is prohibited. However, in an Azure eco-system, this permission is often needed so that we provided an Azure RBAC OSB marketplace service which checks the roles and principal Ids in order to prevent privilege escalation. In the same time, we collect feedback from our users and they complain that many Azure Out-of-the-box Biceps/ARM templates do not work anymore. That is why we reconsider our intitial approach and want to allow RBAC to our project admins - under certain conditions (privilege escalation). What we would need herefore is the ABAC support for Azure Role-Mappings for Azure landing zones. The following article describes the concept: https://learn.microsoft.com/en-us/azure/role-based-access-control/delegate-role-assignments-overview?tabs=template#a-more-secure-method-delegate-role-assignments-with-conditions-preview

As a platform owner I want to update tags and also change their type (for example from single select to multi select) because actually I must delete the tag and parts of the policies the tag is used recreate all in the ui which is very errorprone

I would like to introduce a new mandatory tag for analytics purposes in our company, so that the requirement to fill out this tag is immediately visible for each Project/Workspace without requiring me to communicate to all users and users to manually navigate to the settings page, ensuring consistent tagging across all Projects/Workspaces.

I have a tag with 20+ values defined for workspaces. When I want to introduce this tag on another object (say building block definitions) or if I need add values, I want to be able to copy or reference the set of values. Right now I have to update them manually or write to support@meshcloud.io so that meshcloud support does it.

Just as a multi-select tag type permits the selection of multiple values from a predefined list, I aim to create a tag that allows the entry of multiple free-text values or values that conform to a specified regular expression.

Centralized log management can greatly enhance end-to-end visibility and the security stance by enabling the extraction of audit logs/events from meshStack for import into an external tool such as a SIEM system.

All changes in the settings or other activities in the Admin Area of meshStack should be logged for an audit trail. Its important to know who has changed what when - e.g. to also revert the change if necessary. This includes changes in the: welcome page landing page compliance configuration such as SCIM activation, recertification intervals etc.