SharePoint 2013

OWASP Top Ten to Secure SharePoint Public Site (Part 2)

In part 1, I elaborate what was the challenge in SharePoint default configuration and the default response header produced by WFE. Part-2, I will show how to clean response header and add additional layer of protection. From standard SharePoint deployment, we add a reverse proxy that will act as medium between the user (external client) and the SharePoint farm. So our diagram will change as follow: In computer network, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client form one or more servers.

OWASP Top Ten to Secure SharePoint Public Site (Part 2)

In part 1, I elaborate what was the challenge in SharePoint default configuration and the default response header produced by WFE. Part-2, I will show how to clean response header and add additional layer of protection. From standard SharePoint deployment, we add a reverse proxy that will act as medium between the user (external client) and the SharePoint farm. So our diagram will change as follow: In computer network, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client form one or more servers.

OWASP Top Ten to Secure SharePoint Public Site (Part 1)

In this post I will share how to secure SharePoint public site and follows the recommendation of OWAPS Top Ten. OWASP Top Ten is a powerful awareness document for web application security. It represents a broad consensus about what the most critical web application security flaws are. The goal here is to apply the changes to SharePoint standard installation as minimal as possible, so that the security rules will be applied independently.

OWASP Top Ten to Secure SharePoint Public Site (Part 1)

In this post I will share how to secure SharePoint public site and follows the recommendation of OWAPS Top Ten. OWASP Top Ten is a powerful awareness document for web application security. It represents a broad consensus about what the most critical web application security flaws are. The goal here is to apply the changes to SharePoint standard installation as minimal as possible, so that the security rules will be applied independently.

Check Office 365 Roadmap!

As many or my clients are now moving to Office 365, the cloud version of SharePoint, Exchange and their variants. I lose my control on patches and upgrade to the platform. In the past, our team control and advise the customer of new releases, features and create plan for the delivery to on-prem environment. Nowadays, this role has been taken by Microsoft's team. We are no longer in charge of validation and releasing those patches.

Check Office 365 Roadmap!

As many or my clients are now moving to Office 365, the cloud version of SharePoint, Exchange and their variants. I lose my control on patches and upgrade to the platform. In the past, our team control and advise the customer of new releases, features and create plan for the delivery to on-prem environment. Nowadays, this role has been taken by Microsoft's team. We are no longer in charge of validation and releasing those patches.

Introducing Solution Deployer Nuget

cakriwut - Sep 1, 2014Introducing Solution Deployer Nuget http://t.co/DFm1RCSuuB

Introducing Solution Deployer Nuget

cakriwut - Sep 1, 2014Introducing Solution Deployer Nuget http://t.co/DFm1RCSuuB

Introducing Solution Deployer Nuget

English SharePoint Solution Deployer, by Matthias Einig has been around from 2012. You can find it in Codeplex - SPSD SharePoint Solution Deployer here. Initially it was targeted for SharePoint 2007 deployment but has been evolved many times and now it support SharePoint 2010 and SharePoint 2013. There is big change from SPSD SharePoint 2007 and SPSD SharePoint 2010/2013 version. The former is using MSBuild task to perform the delivery, while the later is using PowerShell to do the delivery.

Introducing Solution Deployer Nuget

English SharePoint Solution Deployer, by Matthias Einig has been around from 2012. You can find it in Codeplex - SPSD SharePoint Solution Deployer here. Initially it was targeted for SharePoint 2007 deployment but has been evolved many times and now it support SharePoint 2010 and SharePoint 2013. There is big change from SPSD SharePoint 2007 and SPSD SharePoint 2010/2013 version. The former is using MSBuild task to perform the delivery, while the later is using PowerShell to do the delivery.