- Source: SekChek Local
SekChek security audit and benchmarking toolset dating from 1996.
History
SekChek was formed by two former auditors from Deloitte and Touche in 1996. The toolset was a set of automated processes to analyse the logical security profile of a computer.
The concept and initial version of SekChek was brought to Deloitte South Africa by Gordon Docherty and Jose Masson, who collaborated on the product design and deliverables with Chris Little CISA, CISSP from Deloitte's Computer Assurance Services Division in Sandton, South Africa. The first version analysed the control parameters for AS/400 systems. While the concept was good, the main concerns at the time were that (a) the clients had to send their operating system security files off-premise to SekChek for processing, and (b) the generated reports highlighted every parameter that wasn't in line with SekChek's world view of best practice. This led to reports of hundreds of pages being produced, with minimal prioritisation of the parameters to fix. Over time, these reports became more concise and user-friendly.
On 20 March 2018 SekCheck's website gave notice operations would cease on 31 May 2018. Reasons cited included SekCheks' business model being less relevant to the business environment in 2018, a surge in compliance and regulatory requirements including GDPR and monetary difficulties due to losses with the insolvency of a credit-card processor.
Products
The SekChek Classic product gathered information on a host which would then be sent encrypted to SekChek for report processing and enable checking security policies had been correctly configured. This originally worked on AS/400 but the number of platforms were extended in the next two years to encompass ed to Windows, Netware and Unix. Reports anonymously compared machines against the average from similar industry computers. The company introduced the Local version of its product in 2008 which avoided the need send data off-site. For windows there was a utility to specifically audit the Active Directory (AD) at domain level rather that at server level which was analyzed by the SAM tool.
Reception
The product was initially marketed as a security evaluator and was noted for providing comprehensive reports of the security vulnerability of a computer system.
References
"Audit Programs & ICQs". isaca.org. Archived from the original (Fee required) on 2007-07-11. Retrieved 2018-12-13.
"Annual Specialist IT Audit Activity Report 2004/5" (PDF). LB Bromley Internal Audit Report. November 2006. Archived from the original (PDF) on 2011-08-27. Retrieved 2009-05-20.
Carroll, Mariana (November 2006). "An Information Systems Auditor's Profile" (PDF). UNISA Dissertation. These reports can be used to identify weaknesses as well as risk ratings and suggested corrective actions. These statements are supported by Mookhey (2004) when he asserts that "the use of these tools for security auditing is prevalentand driven mainly by the inherent complexity within information systems.
External links
SekChek Home Page
