Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Third Party entities improvement #1450

Open
ArchdukeNavaron opened this issue Jan 30, 2025 · 2 comments
Open

Third Party entities improvement #1450

ArchdukeNavaron opened this issue Jan 30, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@ArchdukeNavaron
Copy link

It would be nice if you could document the address of the HQ so that you can easily get an overview of your vendors' current geographic situation.


Allow the configuration of relationships between entities so that you can document sub-processors.


Additionally, it would be nice if you could configure multiple Entities to provide the same solution.
E.g., you could have multiple S3 providers.
Currently, it is impossible to configure a solution that multiple entities can provide.


Allow configuration of recurring audits.
For example, according to ISO27001, you should assess your Third-Party Vendors regularly to check if they are still compliant with your requirements.


Remove the built-in info because, in 99.9% of cases, it does not provide useful information to the user.
Make it dynamic? (when it is built-in, add this information; otherwise, remove it)


Provide information about associated risks on the entity page.
Whenever you create a risk assessment for a vendor's solution, you will most likely end up with some accepted risks.
Therefore, the present and accepted risks should be clearly visible on the entity page.


Consider introducing compliance and risk information on the entity list.
This would also improve the general overview of the current status of your vendors.

@ArchdukeNavaron ArchdukeNavaron added the question Further information is requested label Jan 30, 2025
@ab-smith ab-smith added enhancement New feature or request and removed question Further information is requested labels Jan 30, 2025
@ab-smith
Copy link
Contributor

ab-smith commented Jan 31, 2025

great inputs @ArchdukeNavaron , thank you!
I don't get this specific one though:

Remove the built-in info because, in 99.9% of cases, it does not provide useful information to the user.
Make it dynamic? (when it is built-in, add this information; otherwise, remove it)

@ArchdukeNavaron
Copy link
Author

@ab-smith on the Entities overview, there is information whether or not this entity is built into CISO Assistant.
But how many built-in entities will there gonna be?

Because if it is only one or so, I think it should just be removed, because in most cases, it will not be a built-in entity.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants