cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SQLAnywhere 17 - Stop direct access to database

1,190

We are trying to secure a SQL Anywhere (v17) database used by our application.

Ideally we want all access to the database to be through our application only. Currently its quite easy to discover the username/password used by our applications ODBC connection to the database.

What options do we have to further secure our database and stop any connections that don't originate from our application?

We have considered using the login_procedure option to write logic to only accept connections from our applications full path / filename taken from AppInfo, and applying this to all connections. The general idea stems from this post.

Would this be enough, or is there some way this could be bypassed? (without our users renaming their application and moving it into the approved path - we aren't concerned about this scenario as it is unlikely given how heavily used our application is).

Are there better solutions to locking down the database, given that our application is currently dependant on one username/password which has access to most tables? (We understand this itself isn't ideal - but changing it would require a lot of redevelopment)

We would appreciate any insights

View Entire Topic
0 Kudos

Hello this is Gulshan Negi

Well, in order to prevent unauthorized access, multiple layers of security measures must be implemented when securing a SQL Anywhere database that is utilized by an application. This can incorporate application-level security utilizing the login_procedure choice, encryption and confirmation components, client level security, normal observing and evaluating, keeping your information base and application cutting-edge, and following the guideline of least honor. It is essential to evaluate and put into place appropriate security measures that are tailored to your particular environment and requirements. If you require assistance, you should seek the assistance of knowledgeable database administrators or security experts.

Thanks