d01033b7d337212fcd6f543be132210c7b8921d4
Integration/Tutorials/Security.md
| ... | ... | @@ -143,7 +143,7 @@ public static void InitializeReporting() |
| 143 | 143 | ``` |
| 144 | 144 | ### Preventing URL Cross Scripting |
| 145 | 145 | |
| 146 | -In order to make sure a URL doesn't allow JavaScript injection, you must make sure that in your web.config that a page element has the validateRequest attribute set to true as you see |
|
| 146 | +In order to make sure a URL doesn't allow JavaScript injection, you must make sure that in your web.config that a page element has the **validateRequest** attribute set to true as you see |
|
| 147 | 147 | |
| 148 | 148 | Request Validation Source: [MSDN Request Validation](http://msdn.microsoft.com/en-us/library/hh882339%28v=vs.110%29.aspx) |
| 149 | 149 | Modified Webconfig Source: http://archives.izenda.us/ri/webforms-cs.zip |
| ... | ... | @@ -157,7 +157,7 @@ Modified Webconfig Source: http://archives.izenda.us/ri/webforms-cs.zip |
| 157 | 157 | <!-- Needed on .NET 4.0 |
| 158 | 158 | <httpRuntime requestValidationMode="2.0" /> |
| 159 | 159 | --> |
| 160 | - <pages **validateRequest="true"** enableEventValidation="false" viewStateEncryptionMode="Never" /> |
|
| 160 | + <pages validateRequest="true" enableEventValidation="false" viewStateEncryptionMode="Never" /> |
|
| 161 | 161 | <customErrors mode="Off"> |
| 162 | 162 | <error statusCode="403" redirect="NoAccess.htm" /> |
| 163 | 163 | <error statusCode="404" redirect="FileNotFound.htm" /> |
| ... | ... | @@ -169,4 +169,8 @@ Modified Webconfig Source: http://archives.izenda.us/ri/webforms-cs.zip |
| 169 | 169 | <mimeMap fileExtension=".json" mimeType="application/json" /> |
| 170 | 170 | </staticContent> |
| 171 | 171 | </system.webServer> |
| 172 | -``` |
|
| ... | ... | \ No newline at end of file |
| 0 | +``` |
|
| 1 | + |
|
| 2 | +###Determining user privileges |
|
| 3 | + |
|
| 4 | +Another consideration to take into account when setting up security with Izenda is to use a restricted database user account in your connection string. Every relational DBMS supported by Izenda uses some kind of database server security model, and we encourage our customers to take full advantage of that. Restricting access to create or delete tables, restricting which schemas are able to be viewed, and which stored procedures can be executed are important considerations in any instance where a new entry point is introduced to a secure or sensitive system. |
|
| ... | ... | \ No newline at end of file |