計算機(jī)外文翻譯--數(shù)據(jù)庫安全-文庫吧資料
2025-05-21 17:20本頁面
【正文】 red. If normal user access is acceptable, then 畢業(yè)設(shè)計（文獻(xiàn)翻譯） 第 8 頁 apply this restriction. Again the problem of SQL security is not totally a database issue. Specific database mand or requests should not be allowed to pass through the application layer. This can be prevented by employing a “secure coding” approach. Again this is veering offtopic, but it is worth detailing a few basic steps that should be employed. The first step in securing any application should be the validation and control of user input. Strict typing should be used where possible to control specific data (. if numeric data is expected), and where string based data is required, specific non alphanumeric characters should be prohibited where possible. Where this cannot be performed, consideration should be made to try and substitute characters (for example the use of single q uotes, which are monly used in SQL mands). Specific securityrelated coding techniques should be added to coding standard in use within your organization. If all developers are using the same baseline standards, with specific security measures, this will reduce the risk of SQL injection promises. Another simple method that can be employed is to remove all procedures within the database that are not required. This restricts the extent that unwanted or superfluous aspects of the database could be maliciously used. This is analogous to removing unwanted services on an operating system, which is mon security practice. ◆ Overall In conclusion, most of the points I have made above are mon sense security concepts, and are not specific to databases. However all of these points DO apply to databases and if these basic security measures are employed, the security of your database will be greatly improved. PART 2 The next article on database security will focus on specific SQL and Oracle security problems, with detailed examples and advice for DBA and developers. There are a lot of similarities between database security and general IT security, with generic simple security steps and measures that can be (and should be) easily implemented to dramatically improve security. While these may seem like mon sense, it is surprising how many times we have seen that mon security measures are not implemented and so cause a security exposure. 畢業(yè)設(shè)計（文獻(xiàn)翻譯） 第 9 頁 ◆ User account and password security One of the basic first principals in IT security is “make sure you have a good password”. Within this statement I have assumed that a password is set in the first place, though this is often not the case. I touched on mon sense security in my last article, but I think it is important to highlight this again. As with operating systems, the focus of attention within database account security is aimed at administration accounts. Within SQL this will be the SA account and within Oracle it may be the SYSDBA or ORACLE account. It is very mon for SQL SA accounts to have a password of ?SA? or even worse a blank password, which is just as mon. This password laziness breaks the most basic security principals, and should be stamped
畢業(yè)設(shè)計相關(guān)推薦
鄂ICP備17016276號-1