v3.4.0: More dependable framework updates

Coverage stays consistent during framework changes
Benthic now tracks framework-managed control content with stable identities and
explicit lifecycle decisions. This makes update plans deterministic and keeps
retired package content from being mistaken for current requirements.
Compliance changes are easier to verify
The release adds a durable history of framework-seeded control changes and
stronger checks around imports, replacements, and deletions. Platform operators
can verify each environment before and after an update with exact, repeatable
evidence.
Safer control mapping
Invalid mixed-scope control mappings are stopped before they can affect project
coverage. Existing valid control-level and objective-level mappings continue
unchanged.
Also improved

• Framework update plans now explain why each item is added, retained, retired,

or refused.

• Production receives the same validated application images that completed the

demo qualification path.

Questions or feedback? Reply on this update and tell us where the workflow still
needs work.