
Unofficial Sitecore 8 Training Webinar Series – Session 6
Link to GitHub source.
Continue Reading →The blog

Link to GitHub source.
Continue Reading →
https://attendee.gotowebinar.com/register/8760359272621483523
Continue Reading →

A month ago Mark Cassidy took the initiative to start a Stack Exchange beta site. In doing so we got the community together and got them to commit to the cause. The community rose to the occasion was were quickly in beta. It was the fastest path to beta and other users were questioning how we got here. See the screenshot at the bottom of this post.
Continue Reading →
Sitecore 8.2 was released with Microsoft Dependency Injection. I wanted to try to setup a sample project which utilizes the DI.
Continue Reading →
As most of you know, my favorite is SimpleInjector. I use it in all my projects. Since Sitecore 8.2 was released yesterday (August 30th 2016), I decided to do a performance benchmark against Microsoft Extensions DependencyInjection which is used as part of Sitecore to provide DependencyInjection.
Continue Reading →
We have been going through XSS vulnerability in the past two posts. I am going to end this series with one last post about Secure Headers. We will go through a few headers that we can implement.
Continue Reading →
In the last Cross Site Scripting (XSS) post: Secure Sitecore : Cross Site Scripting (XSS) Vulnerability Findings , we looked at how these attacks might look based on the browser the user is using. The interesting factor is that a potential attacker might not use a browser at all. You do not need a browser to initiate requests and process them. Fuzzing is a common technique where an attacker can create potentially invalid requests from scratch to perform testing on applications, to see how they respond.
Continue Reading →
Lately I have been focussed on OWASP Top 10 security guidelines and locking down sites. The next one on the list is Cross Site Scripting (XSS). According to OWASP:
Continue Reading →
Lately I have been focussed on OWASP Top 10 security guidelines and locking down sites. The next one on the list is Response Headers. For reach page request, the server sends over the headers containing information about the server and ASP.NET. Some call it chatty headers and less we send back the better it is to protect ourselves.
Continue Reading →
Enable custom errors to restrict users from seeing sensitive information such as the paths, stack trace and .NET version information. A potential hacker can get a lot of information on your environment just by looking at the default error page.
Continue Reading →
This blog post will go through how I setup my solution to be able to read everything I need from configuration rather than hardcoding it as part of code.
Continue Reading →