Release v3.3190.0 (Nov 5 2021)
Applies to: Guardian
Written by Cliff Hobbs | Last published at: December 14, 2022
Website v3.19.1
Fixed Issues
- Job Schedule > UTC not being accepted as valid time-zone, error showing zero hour (after midnight) or zero minutes
- CIS benchmark scheduled jobs aren’t running at their scheduled times
- AWS Windows instance added using default CM
- Change Report > Report cover missing Result Type value
- Benchmarks > Dynamic Node Groups not available in filter
- CIS API failing when using filters
- AWS EC2 Instance Config scan created with node name as region
- Event Action fault typing left sqbracket
- Add Node > Add duplicate node name causes a 422 error and page hangs
- Edit AWS Sync Job > “Validation failed: Source can’t be blank” error message
Enhancements
- Change login screen to say “Active Directory” credentials instead of “Windows” credentials
- Button in settings page on prem to reboot UI
- Azure nodes should use Client Secret instead of username/password
- Customer needs to update appliance through UI
- Need a way to restart the appliance from the UI
- Check for orphaned CIS exclusions
- Link to examples of liquid input for event actions
- AWS Sync job won’t start
- Run scheduled job on demand
- New Monitored Page > Extend the amount of text viewable before truncation
- System Alert Event for disk space issues
- Integration details in Events for detected nodes
- CIS October Update
SSH Connection Manager/Agent v5.8.2
Fixed Issues
- CloudWatch detects dashboards as separate nodes
Enhancements
- Integration details in events for detected nodes
- AWS Policies
- IAM Access Analyzer Node
- Cloudwatch Node
- KMS Node
- AWS Config Node
- SNS Node
- CloudTrail Node
- Improve error reporting and handling when SFTP is not present or misconfigured
- Handle Palo Alto password change prompts with appropriate error message
- Github repo archived status