Use role-based access control (RBAC) in Puppet Remediate to ensure that each user has the access and permissions appropriate to their role on the team.

The "role" in role-based access control refers to a system of user roles, and each role contains permissions which define what a user can or can't do within Remediate. There are two default user roles: Administrator and Viewer.

RoleUsernameDefault passwordPermissions
Administratoradmin@Admin
  • Add and remove sources and credentials.

  • Upload scripts and modules.

  • Run tasks.

  • View dashboards.

  • View all node, package, container listing and details pages.

Viewerviewer@Admin
  • View dashboards.

  • View all node, package, container listing and details pages.

To change the default passwords, run the following commands:
docker-compose run remediate set-admin-password
docker-compose run remediate set-viewer-password

Discovery events

The Recent events page provides the following information about each discovery run which, by default, occurs every 4 hours.

Event detailDescription
Total jobsTotal number of jobs relating to the discovery event. Each discovery event has two jobs:
  • Discover the node.

  • Discover resources on the node.

FailedTotal number of failed jobs.
StatusThe event status.
StartedDate and time the discovery run started.
StatusThe job status:
  • Succeeded

  • Failed

  • Pending

  • Running

SourceYour configured source: vulnerability scanner or infrastructure source.
Job detailsThe number of facets discovered. Each facet represents a set of related attributes, each one independently maintained, that describe a certain aspect of a discovered resource; node, package, or container.
Completion timeThe time the discovery run completed.

Tasks events

The Task event page provides the following information about the task that was ran on nodes.

Event detailDescription
Total jobsTotal number of jobs relating to the task event. Each task event has two jobs:
  • Run task on node.

  • Discover resources on the node.

FailedTotal number of failed jobs.
StatusThe event status.
StartedDate and time the event started.
StatusThe job status:
  • Succeeded

  • Failed

  • Pending

  • Running

SourceYour configured source: vulnerability scanner or infrastructure source.
Job detailsThe command output from running the task and the number of facets discovered. Each facet represents a set of related attributes, each one independently maintained, that describe a certain aspect of a discovered resource; node, package, or container.
Completion timeThe time the task completed.
Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.