Security Testing

Many times we miss security testing or we will do in last minute. Due to this we dont have enough time to fix the issues or we may put application into production with security risks. What we need to do?

Step 1: Plan Security Testing as part of Testing efforts.

Step 2: Educate developers about security risks in application

Step 3: Do security testing earliest and fix issues as early as possible.

Some links for reference.

Open Web Application Security Project (OWASP) – http://www.owasp.org

An introduction to SQL injection: http://www.net-security.org/dl/articles/IntegrigyIntrotoSQLInjectionAttacks.pdf

SQL Injection: http://www.securiteam.com/securityreviews/5DP0N1P76E.html

SQL Injection by example: http://unixwiz.net/techtips/sql-injection.html

https://www.qualys.com/

http://www.veracode.com/products/static-analysis-sast/binary-code-analysis

Fortify – http://www8.hp.com/us/en/software-solutions/static-code-analysis-sast/index.html?

-o-

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s