In this article, you will discover how to use and navigate in the scope interface on the platform
SUMMARY
The My Yuno perimeters page allows you to manage the elements relating to your Yuno scopes
List of perimeters
The home page lists the perimeters created within your company.
Scopes and user rights :
The My Yuno perimeters page only displays the perimeters that you, as a user, have the right to view.
Thus, an administrator will have an exhaustive list of all the perimeters created, whereas a regular user (regular_user profile) will only see the perimeters in which he is registered.
Several information are associated with the different scopes :
1. The name
2. The number of technologies associated with the scope
3. The number of users registered in the scope
4. The number of technical components associated with the scope
5.The number of open action tickets associated with the scope
6. search for a specific perimeter
From this page you can also :
8. delete an existing scope
9. export the list of action plans : you will recover an excel file containing all the action tickets associated with your perimeters (one tab per scope).
10. export the list of scopes: you will recover an Excel file containing :
- a tab summarising the statistics related to your scope (number of scopes, technologies monitored, registered users, etc.)
- a tab for each scope detailing the technologies associated with each scope
Finally, you can quickly access certain characteristics of your scopes :
- The user icon takes you to the list of users registered in the scope
- The technologies icon takes you to the list of technologies associated with the scope
- The technical component icon takes you to the list of technical components in the scope.
Click on the name of the scope to access its details.
Scopes details
The characteristics of the scope are divided into several tabs :
Users tab
This tab groups together all the characteristics of the scopes related to the users associated with the perimeter.
Here you will find the list of users associated with the scopes:
1. The User name
2. The number of associated action tickets
3. The number of scopes in the audit module with which the user is associated
4. The number of scopes in the Yuno module with which the user is associated
5. The number of Serenety module perimeters with which the user is associated
You can also perform the following actions:
6. Search for a user by name
7. Add a user to Yuno
8. Associate a new user with the scope
9. Remove a user from the scope
10. Grant or deny the user write rights to the scope
Finally, by clicking on the user's name, you are redirected to his page
Details tab
In the details tab, you will find all the information relating to the creation of the perimeter :
1. The name of the perimeter
2. The perimeter owner
3. The remediation manager for the scope
4. The association with a parent scope
5. A potential description of the scope
Preferences tab
The Preferences tab is used to set up the association of bulletins with the scope and the generation of scope action tickets.
Deployed technologie(s) tab
The deployed technologies tab allows you to determine which technologies you wish to track within this scope.
On this page you can consult the list of technologies associated with the scope, but also :
1. Remove technologies from the scope
2. Associate new technologies with the scope
In the add window you will find the list of all the technologies currently monitored by XMCO.
Tick the technologies you want to be associated with your scope.
You can also filter technologies by publisher or by technology name.
The "select all" and "remove all" buttons can be used to :
- tick all the selected technologies (taking into account the filters)
- uncheck the entire selection of technologies (taking filters into account).
This allows you to add/remove technologies from your scopes in bulk.
Technical components tab
List of technical components associated with the scope.
What is a technical component ?
In Yuno, the technical component offers an additional level of granularity in your remediation management.Indeed, it gives you the opportunity to integrate a notion of asset present in your information system.
The information of the technical component impacted by a vulnerability/Patch/exploit will be displayed on each of your action ticket.
The technical components are shared with the audit module.
List of the technical components
This tab lists all the technical components contained within the scope in question.
For each component, you will find :
1. Its name
2. The number of associated action tickets
3. The number of associated technologies
4. The number of scopes in which the technical component can be found
5. The number of audits involving this technical component
By clicking on the name of the technical component, you can access the list of action tickets associated with the technical component, all scopes included.
Create new technical components
By clicking on the + you can add a technical component to Yuno. This can then be associated with the scope in question.
In the pop-up window that opens, you will need to enter :
- The name of the technical component (required)
- The type of component (required)
- Indicate which technologies are present in the technical component. This will enable us to link the correct action tickets to the technical component.
- You can also add a description for the component.
Once the component has been added, you can associate it with the scope by clicking on the dedicated button.
Linking existing technical components to the scope
To associate a technical component with the scope, click on the button and then select the technical component from the pop-up menu. Click on "Add" to confirm the association.
Action plan tab
This tab contains all the action tickets associated with the scope.
Refer to the Action Plan page for more information.
Statistics
Using the date selector, this tab contains statistics on the following information :
- Yuno bulletins associated with the scope, created during the selected period, broken down by criticality.
- Yuno bulletins associated with the scope, created during the selected period, broken down by type.
- Action tickets associated with the scope as they were during the period, broken down by criticality. Thus, you can estimate how many critical action ticket were present from january to august 2022.
- Action tickets associated with the scope as they were during the period, broken down by status. Thus, you can estimate the quantity of "accepted risk" tickets from january to august 2022.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article