@@ -1321,7 +1321,6 @@ These requirements apply to the product, regardless of the product's use case an
The requirement **AAC_AUTH-5:** is intentionally vague.
The model can be complex, and there can be multiple different overlapping mechanisms in place that can be used to enable the same function.
The authoritative decision making requirement listed as **AAC_AUTH-11:** directs the product not to cache the credentials.
While the requirement calls for active checking, in combination with **AAC_AUTH-4:** the wording leaves room to implement a fluent GUI experience when viewing the content and performing privileged actions are separated.
