Updates

VERSION 1.5.3 - Additions/changes

I have added a new field to the preferences page: "List pf files to rename:"

The field consists of a list of comma separated file names to be re-named on discovery. If found, these files will be re-named by giving them a " _renamed.by.ssam" extension. This feature might be useful where you know of certain file names that have caused you problems in the past. Re-naming the file as soon as it is detected, will prevent it being used for malicious purposes. An email alert will be sent on detection.

I have added some extra utilities, as follows:
Google malware check - uses google safe browsing diagnostic page.
Check your sites with the VirusTotal API. Checks if your site is black-listed on up to 30+ databases, including MalwareDomainList, Yandex Safebrowsing, MalwarePatrol, Phishtank, SpyEyeTracker and many others.
SiteTruth Ratings Summary. SiteTruth ratings are based on public or commercially available information, automatically gathered from multiple sources including public records and business credit ratings. They reflect the legal and commercial legitimacy of the business, not consumer opinion or satisfaction.

VERSION 1.5.2 - Additions/changes

Prior to this version, SSAM would not perform a recursive scan on a Windows/IIS server. It would only scan the root, or nominated directory. SSAM is now compatible with Windows/IIS and will perform a full recursive scan.

I have added the ability to ignore directories during the scan. This can be useful on very large sites or with password protected directories, where scanning may not be necessary.

The time taken to scan a site has been decreased. Especially where the user has nominated directories to be ignored.

VERSION 1.5.1 - Additions/changes

Added a file comparison utility, accessible via a new button on the 'Preferences' page (index.php). Courtesy of: Ross Scrivener http://scrivna.com PHP file diff implementation. Much credit goes to... Paul's Simple Diff Algorithm v 0.1 (C) Paul Butler 2007 http://www.paulbutler.org Used and distributed under the zlib/libpng license.

Added ability to download modified files from the SSAM log display. This will allow the user to download the file to local machine, for eventual comparison with a backed up copy, using the file comparison utility mentioned above. Any request to download a file that receives an HTTP error, will not be available for download. E.g. file not found or password protected.

Changed FTP/DB text boxes to password boxes on the setup page (index1.php). Even with this change, it is very important to make the SSAM directory password protected, as there will be other sensitive data displayed in the form and passwords are not encrypted when passed to the file index.php.

Changed info icons on all pages from onHover to onClick event. User request.

Fixed most of the Internet Explorer CSS bugs that were in v1.5.0 - Still not perfect, so IE is not recommended

 

Installation

QUICK START

Download SSA and unzip the contents. Choose a web site that will act as your 'Master' site Upload all the SSA files to a password-protected directory, directly off the site root, e.g. mastersite.com/ssa Run the file 'index1.php', submit the settings form for each site you wish to monitor and click 'Finished'. This will take you to the preferences form, where, once details are submitted for all your sites, you will be able to run the script and view your logs.

RESTRICTIONS

When scanning a site on a Windows/IIS server via FTP, it is not possible to detect changes in file permissions. Therefore, these changes will not appear in the log.

Not so much a restriction, more the nature of the beast. The FTP scan time can vary, depending on, the size of the monitored site, connection speed and conditions between the 'Master' site and the target site. For example, a site with about 5000 files should take about 8 seconds. Larger sites will take longer. It may be necessary, with very large sites, to increase your PHP time-out setting. The time taken should also be considered when setting up Cron jobs. They will need to be spaced out accordingly.

FILE AND DIRECTORY NAMES

All file names must remain as is. The SSA directory can be named anything you like.

FILE PLACEMENT

1. If it doesn't already exist, a 'logs' directory will be created during the set up process. It will be created as an OFFLINE directory, just ABOVE root level, where it is not web-accessible. A file named db_settings.txt will be created in the 'logs' directory, inside a sub-directory with the same name as the web site being monitored, e.g logs/domain.com. This file contains database access details (password is encrypted). FTP access details are stored in the database (password encrypted).

2. Create a directory, just BELOW root level, where you will upload the SimpleSiteAudit files. Name this directory what ever you like, e.g. 'ssa'. This directory should be password protected as it will contain access to sensitive information.

RUN THE SETTINGS PAGE (index1.php)

1. Upload the files to your new directory and run index1.php in your browser.

2. Complete and submit the FTP and database settings for each site you want to monitor, and then click 'Finished' to move on to the preferences form. Once this is submitted, you are ready to make the first scan.

MONITORING SUB-DOMAINS OR SUB-DIRECTORIES

To monitor a sub-domain or sub-directory, the field 'Document root of site being monitored', in the FTP/db set up page, should be entered as, e.g. htdocs/sub-dir-name or the sub-domain-name - a sub-directory can be added to the sub-domain-name if required, e.g. sub-domain-name/sub-dir-name.

CREATE AN SSA LOG FILE

The settings form allows the optional creation of a log file, containing all the SimpleSiteAudit script outputs. Details will be saved to the database on the 'Master' server. This table can grow quite large, periodic clearing of the table is recommended, and ability to display and clear the table will be provided after the first changes have been detected.

SETTING UP YOUR CRON JOB

During the SSA set up process a special file, named '_remotewebsitename.tld.php' will be created in the SSA directory for each site being monitored. Your Cron jobs should be aimed at these files, e.g./htdocs/ssa/_remotewebsitename.tld.php - This mechanism saves the need to pass parameters from your Cron job to the script, which is restricted by some ISPs. if you are monitoring more than 1 web site, make sure your Cron jobs are adequately spaced out.

DISPLAYING YOUR CRON LOG FILE (Field: 'Path to, and name of your Cron log')

This must point to your Cron log file, i.e. the relative path from your SSA installation files. e.g. ../../cronfilename.txt The 'view file' button will not appear if this file does not exist. Recommend leaving this field empty if using the SSA log file and vice versa. The log contents will appear in a read only textarea. Further formatting is not possible due to unknown input by the Cron process itself. There is no 'Clear log' button for this feature.

SECONDARY USES

There may be other uses for this software, for example, it could be used to notify someone, or a group of people, that certain files had been uploaded and are now available for download or viewing. I’d be interested to know what other uses it has been put to. Please use the 'Feedback' link.