Skip to main content

Azure App Service support now vulnerability scanning

A new great feature is available for Azure App starting from today. How nice would be if you could scan your Azure App to check if you have any kind of security issues.
For example if you develop a web application, it would be nice to be able to scan your application and check if there are any kind of security vulnerabilities.
Until now, this could be made with external partners, not directly from Azure Portal. Starting from now we can do this using Tinfoil Security. You can activate this service directly from Azure Portal. This service is offered using the Marketplace.
There are different tires, that allow you to check your site from one time per week (for 3$/month), and you can scan even twice per day for 500$/month. This feature go hand in hand with if you are using different deployments slots for your web applications. You can scan for integration or pre-production environment for security vulnerabilities before releasing a new version or a hot fix.
In this way, the development team can have a real time feedback, in a very short period of time.

There are a lot of vulnerabilities that are checked by Tinfoil automatically, like Cross-Site-Scripting (XSS).
I invite you to try this new feature.
Also, another benefits of this partnership is also the way how you buy this products - "SaaS". You
pay a monthly subscription. When you don't need anymore this service, you can unsubscribe from this service.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…