KNOWLEDGEBASE · ASP.NET
ASP.NET - security exception errors
Last updated 2025-06-18
ASP.NET Trust Level and Permission Restrictions
On certain occasions, your ASPX files may not function as expected. You might encounter “Permission Denied” or “Security Exception” errors. This is typically due to the default security configuration of the ASP.NET environment on our servers.
🔐 Trust Level Configuration
We have configured ASP.NET Trust Level to MEDIUM in the MACHINE.CONFIG file. This level enforces a secure runtime environment by restricting application capabilities, as summarized below:
Full
Unrestricted permissions. Full access to OS-secured resources and privileged operations.
High
Cannot:
• Call unmanaged code
• Use serviced components
• Write to the event log
• Access Microsoft Message Queuing (MSMQ)
• Use OLE DB data sources
Medium
Includes all High restrictions, plus:
• File access limited to the application directory
• No registry access
Low
Includes all Medium restrictions, plus:
• No SQL Server access
• Cannot assert security permissions
Minimal
Only execution permission is available; no file, network, or resource access is allowed.
If your application requires broader access or you're encountering errors due to these restrictions, please submit a support ticket. In most cases, we can resolve the issue by making specific exceptions or isolations for your website environment.
Tell us what has to stay up.
A short conversation with an engineer. No quote-bot, no callback queue. We'll tell you honestly if we're not the right fit.