Users and Groups
Tenable One Cloud Exposure allows managing user/group access to the console via API. To learn more about managing user access via the console, see Manage Users and Groups in the Tenable Cloud Exposure User Guide.
Scopes:
Managing users/groups in Cloud Exposure requires assigning each user/group with a role and a scope.
A scope can be any of the following types:
- Entire organization - use
{"ScopeId": null}when creating aUserRoleAssignment. - Specific cloud provider - use
awsRoot,azureRootorgcpRootasScopeId - Organizational folder - use the underlying
Idreturned by queryingFolders. - CIPS tenant - use one of the following as a
ScopeId - AWS Account ID
- Azure Subscription ID
- GCP Project ID
To learn more about scopes, see Create an Account Hierarchy with Folders in the Tenable Cloud Exposure User Guide. To learn more about the different roles and permissions available in Cloud Exposure, see Manage Users and Groups in the Tenable Cloud Exposure User Guide.
List all users and roles
NoteYou must have Administrator role permissions to run this command.
query {
UserRoleAssignments {
Role
ScopeId
UserId
}
}Sample response
{
"data": {
"UserRoleAssignments": [
{
"Role": "Administrator",
"ScopeId": "awsRoot",
"UserId": "[email protected]"
},
{
"Role": "Administrator",
"ScopeId": "66cd5e95-76d7-4e99-870c-aebf3cda945f",
"UserId": "[email protected]"
}
]
}
}Add a user with a Viewer role for the entire organization
NoteYou must have Administrator role permissions to run this command.
# TODO: Fill the correct e-mail address and scope
mutation {
CreateUserRoleAssignment(input: {Role: Viewer, UserMail: "[email protected]", ScopeId: null}) {
UserRoleAssignment {
Role
ScopeId
UserId
}
}
}Add a group with a Viewer role for the entire organization
NoteYou must have Administrator role permissions to run this command.
Before you can add a new group, follow the steps to enable Console login via SSO for your IdP by:
- establishing trust between your IdP and Tenable.
- configuring group mapping for your IdP to send group claims to Tenable.
mutation {
CreateGroupRoleAssignment(
input: {
Role: Viewer
GroupIdentifier: "1111-2222-3333-44444"
GroupName: "DevOps", # Optional
ScopeId: "97200972-0972-0972-0972-123456789012"
}) {
GroupRoleAssignment {
Role
ScopeId
GroupId
}
}
}
NoteThe value that you need to enter for the
GroupIdentifierfield depends on the IdP that the group belongs to, as follows:
- Azure AD: Group ID
- All other IdPs: Group name
GroupNameis an additional, optional field that is relevant for Azure AD.
Sample response
{
"data": {
"CreateGroupRoleAssignment": {
"GroupRoleAssignment": {
"Role": "Viewer",
"ScopeId": null,
"GroupId": "1111-2222-3333-4444"
}
}
}
}Updated 7 days ago
