Rule updates to support Content 2.0
Yes, we are currently adding additional capabilities to the ESU installer to detect the dependencies on RSA supplied rules. Please be sure to read the release notes as well as they may contain additional instructions or limitations about this.
Is there going to be a Content 2.0 Roadmap? It looks like some of the devices of a common family (Unix for example) are not getting migrated all at once.
Also, are Content 1.0 rules going to continue to get updates after the Content 2.0 option has been provided?
We don't have a device specific Content 2.0 roadmap per se but we are updating devices to Content 2.0 during our normal update cycles. We had looked at converting all products by device category to move blocks of devices to Content 2.0 but it would have consumed all of our content resources and we would have been unable to deliver critical updates to devices in a timely manner. For example if you want an update to specific FW product, but we had FWs scheduled out 6 months to be converted as a block, it would have a significant impact on time to market. Not all devices, within a device class, are weighted the same so we would have been converting products with a smaller footprint over another product, in another device class, that is more critical. Our device roadmap only goes out 45-60 days to allow for greater flexibility so would be interested in hearing customer's Content 2.0 device priorities and I can work them into our current planning process.
When we migrate a device to Content 2.0 we update all the out-of-the-box reports. Custom reports may still be impacted by the Content 2.0 migration as the tables or variables have changed. We'll have a Report Analyzer tool in the ESU installer in early Q1 and will have a migration guide posted to SecurCare Online shortly.