The stax-audit-bus EventBridge rule has been deprecated and will be removed from all Stax-managed AWS accounts on ** 05**** Feb 2024. **To continue receiving events that the stax-audit-busEventBridge rule is sending to the Security account, please review our guide to prepare for the change.
Stax-managed Security Hub now supports the NIST Special Publication 800-53 Revision 5 standard in all Stax-supported regions. This NIST standard can be activated in Stax-managed Security Hub using the Stax API and SDK. Stax Console support for the standard will be available in early 2024.
On Thursday, the 30th of November 2023, an update will be applied to Stax Compliance to improve performance and reliability.
The update implements security and stability updates to the underlying software. No functional changes will be introduced.
There will be no impact to service expected as a result of this upgrade. Should you experience any issues, please raise a support case.
To ensure you receive notice of upcoming changes to Stax, make sure you're subscribed to the status page.
Stax Workloads are now deployable in any region enabled within the Foundational Service Stax-managed AWS Regions. When initiating a new workload deployment through the Stax Console or SDK, you can choose from default and enabled opt-in regions, such as Melbourne (ap-southeast-4). Visit our help docs for a comprehensive list of all currently supported AWS regions.
Stax now supports enabling AWS opt-in Regions for your Stax tenancy. Configuring an opt-in Region, such as Melbourne (ap-southeast-4), enables the region for all accounts within your Organization and brings them in line with security and best practices through the Stax Assurance process.
See Using Stax-managed AWS Regions for details on configuring AWS opt-in Regions.
Stax Rule Bundles now provide AWS Console remediation guidance, offering organizations actionable steps to address rule violations and maintain compliance. Refer to our guide for more details.
To gain detailed insights into your AWS cost information, or to feed billing information into third-party tools, you can now opt-in to have your Stax-managed AWS Cost and Usage Reports (CURs) exported directly to an S3 bucket in your AWS Organization's logging account. To find out more, see Opt-in to Stax-managed CUR export to the Logging Accountin the docs.
In addition to viewing your rule-level compliance score based on passing and failing rules, Stax Compliance users can now view compliance scores calculated by the number of passing/failing resources. This new resource-level compliance view enables resource-focused operational insights and remediation.
Choose the vertical ellipsis (⋮) under the summary results on the Rule page to change how the compliance score is calculated. See our guide for more details.
What’s Changing? Stax has decided to remove the chat support button from the Cost and Compliance segments of Stax. While this feature is being deprecated, you can communicate with the Stax support team by clicking the “Support” button on the lower left-hand side of the console. This change aligns with our commitment to improving our services and catering to your needs effectively.
If you have any questions, encounter any issues, or require any further assistance with this change, please do not hesitate to contact our support team using the Support button in the lower left of your console or via https://stax.io/support
Thanks, The team at Stax
A number of Rule names have been updated to improve usability and standardize rule names across all Rule Bundles. To find out more, visit the Stax Compliance module guide.