Verifying IPsec Functionality in Event Viewer

After the local IPsec policies are enabled on both SQL1 and SP1, IPsec communications can take place. To test this, either ping the server from the client desktop or perform other network tests, such as accessing SP1’s SharePoint site.

A quick look at the IP Security Monitor that was established in MMC on SP1 shows that IPsec traffic has been initialized and is logging itself. Traffic statistics, such as those shown in Figure 15.11, should subsequently be shown. All communications between the SharePoint farm members are now highly encrypted and secured.

Figure 15.11. Viewing IPsec statistics.

These default IPsec policies are useful in establishing ad hoc IPsec between SharePoint clients on a network but are limited in their scope. Enterprise-wide IPsec policies can be accomplished through the use of group policies, but proper planning of an enterprise IPsec implementation is necessary to effectively secure an entire environment using custom IPsec policies.