Microsoft SQL database client applications must supply credentials in order to authenticate and connect to the database. We often come across customers that are ‘hard-coding’ their database credentials as plain-text directly in their application code, or within application configuration files. This is a security risk.

Anyone with access to the code or the configuration files can obtain the credentials which increases the risk of misuse. It increases the risk of credentials being accidentally or inadvertently shared within code source control repositories (like GitLab for example). In addition, when credentials are hard-coded within source code, it makes it hard to change those credentials on a regular basis without causing disruption, so credentials typically don’t get changed which further increases the risk of potential misuse if credentials are ever compromised.

To read the full blog - download the PDF here -  Technical Blog - AWS Secrets Manager

 

Carbon Neutral
Phone | Zen Internet

Zen Internet - Home SalesSales
01706 902573

Phone | Zen Internet

Zen Internet - Customer EnquiriesCustomer Enquiries
01706 902001