This documentation is archived and is not being maintained.

Secure asserts







Breaking Change


A method asserts a permission and no security checks are performed on the caller.

Asserting a security permission without performing any security checks can leave an exploitable security weakness in your code. A security stack walk stops when a security permission is asserted. If you assert a permission without performing any checks on the caller, the caller might be able to indirectly execute code using your permissions. Asserts without security checks are only permissible when you are certain that the assert cannot be used in a harmful manner, namely, if the code you call is harmless, or users have no way to pass arbitrary information to code that you call.

To fix a violation of this rule, add a security demand to the method or its declaring type.

Only exclude a warning from this rule after a careful security review.