Up to Documentation
How To Use JASP
We see two main usage modes for JASP:
- Checkups - JASP can be used as a point in time check to find issues to remediate.
- Monitoring - JASP checks your environment every day and feeds into a bigger process.
For some organizations, the best workflow is to log into JASP and run a scan on a given environment. The result will include a set of findings which can be remediated one by one or over time by a user navigating the “The One Thing™” screen or by filtering based on a report.
For other organizations, particularly ones where DevOps work is distributed and AWS resources are provisioned on the fly across different AWS accounts, JASP provides daily monitoring of multiple environments so that you can get alerted around new high score findings. This allows developers and DevOps teams to move fast while having a way to identify misses.
Across both paradigms we have three main ways we expect people to consume JASP data:
- The One Thing™ - This screen shows just the single most important thing we think you should do.
- Reporting - The reporting screens allow users to slice and dice and even export data.
- API - Build integrations that drive scans and remediations.
The idea is to support a simple UI built to not overwhelm users, a more advanced UI for advanced users and an open API that can be used to extend the system.