Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i have one web application, with postgresql as DB, evrything is fine..now trying to implement one security feature..that my db should be updated or del or any thing has to done through my application only…and admin also…i.e sort to protecting the db..no one change it back end..and through some application….i need some ideas
What does it mean through your application only? As opposed to changed with direct access to the database?
If that is the case then it is trivial – do not distribute the database password to anyone.
If you need to give access to other applications create separate users/roles for such purpose.
As for django – it provides another layer of security, as described here and you can extend it if it does not fit your bill.