| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Secure development (Reporting Services) |
Learn about the code access security system that Reporting Services uses, which runs code in tightly constrained, administrator-defined security contexts. |
kfollis |
kfollis |
09/25/2024 |
reporting-services |
extensions |
reference |
|
|
The [!INCLUDEmsCoName] [!INCLUDEdnprdnshort] provides a robust security system that can run code in tightly constrained, administrator-defined security contexts. [!INCLUDEssRSnoversion] uses the [!INCLUDEdnprdnshort] security system, known as code access security (or evidence-based security). Under code access security, a user might be trusted to access a resource, but if the code the user executes isn't trusted, access to the resource is denied.
Security based on code, as opposed to specific users, permits security to be expressed for custom assemblies or data, delivery, rendering, and security extensions that you develop for [!INCLUDEssRSnoversion]. Any number of [!INCLUDEssRSnoversion] users might execute your extension code, all of whom are unknown at development time. The custom assemblies or extensions that you develop require specific security policies in [!INCLUDEssRSnoversion]. These security policies are represented as types in the [!INCLUDEdnprdnshort]. For a more information about code access security, see "Code Access Security" in the [!INCLUDEdnprdnshort] documentation.
Code access security in Reporting Services
Introduces code access security and policy configuration for custom assemblies and extensions in [!INCLUDEssRSnoversion].
Understand security policies
Describes the various assembly types in [!INCLUDEssRSnoversion] and how code access security affects code permissions.
Use Reporting Services security policy files
Describes the different [!INCLUDEssRSnoversion] components and the corresponding policy configuration files.