Common terms
| Term | Meaning |
|---|---|
| Workspace | Your team's shared Byrsa environment. |
| Cloud account | An AWS account connected to Byrsa. |
| Resource / asset | A cloud object such as an EC2 instance, security group, bucket, or database. |
| Misconfiguration | A resource configuration that fails a security check. Some pages call these records vulnerabilities. |
| Runtime finding | A security issue imported from Amazon Inspector, often a software-package vulnerability. |
| CVE | An identifier for a publicly reported software vulnerability. |
| Attack path | A potential route through connected resources that helps you investigate security risk. |
| Alert rule | Conditions that decide when and where Byrsa should send a notification. |
| Alert event | A notification occurrence that your team can review and acknowledge. |
| Task | A work item for tracking an investigation or security improvement. |
| Risk exception | A documented decision to accept or set aside an issue for a defined period. |
| Assessment | A review of collected security checks against a framework. |
| First recorded | When Byrsa first added the finding. |
| Closure first observed | When Byrsa first recorded that the finding was closed. |
| Inventory freshness | How recently Byrsa observed a resource. |
For practical examples, start with Misconfigurations, Runtime Protection, or Attack Paths.