Q: What is SecReport?
A: SecReport is a security reporting solution designed to produce human-readable reports of file system permissions.
Q: What are typical use cases for SecReport?
A: SecReport is useful in a variety of scenarios, including security audits, compliance checks, incident investigation, post-migration ACL verification or any case in which the need arises to compile a list of individuals to whom any file system permissions were granted.
Q: What is the purpose of SecReport Web Service component?
A: The Web Service component allows SecReport to function in an unattended mode, running scheduled reports automatically and delivering reports to e-mail recipients. This is an optional component that needs to be installed on a Web (IIS) Server.
Q: What are the trial version limitations?
A: The trial version is bound by two limitations: a working period of 30 days and a maximum of 100 rows per report.
Q: What are the differences between SecReport Enterprise and SecReport Light?
A: SecReport Light and SecReport Enterprise have similar basic functionality providing a security reporting solution designed to produce human-readable reports of file system permissions. SecReport Light can generate reports in an attended mode only, it lacks the capability to schedule reports generation and automatically send them by e-mail. SecReport Enterprise adds these capabilities by introducing a Web Service Component. Note that the user guide applies to both products. Functionality only relevant to SecReport Enterprise is mentioned as such.
Q: Is there a site licensing option?
A: Yes. In order to receive a price quote for a site license, please contact firstname.lastname@example.org.
Q: Is it normal for SecReport to consume large amounts of RAM?
A: When you use SecReport to analyze directory structures with many objects, complex ACLs and advanced options, it is normal for SecReport’s memory footprint to be as high as several gigabytes.
It is strongly recommended to use the 64-bit version of SecReport for analyzing large file systems.
The “Expand primary groups” and “Display objects even if identical to parent” options – when selected, can dramatically increase the size of the reports and the console/service resource consumption.
Q: Does SecReport support double-byte characters and complex languages?
Q: My PDF report layout is different from the layout (sorting, grouping) I have configured using the console. Why?
A: PDF reports have a limited number of customizations available using the “Report Settings” tab. When viewing a report in the console, you can re-arrange columns, sort and group data and export your results to an Excel file exactly as formatted in the console.
Q: Why do some entries in the report show as SIDs instead of user / group names?
A: Typically, this is an environmental issue not related to SecReport, stemming from the failure to map a SID to an account name. This can result from orphaned accounts, local accounts from computers or domains that are no longer accessible, etc.
Q: Some of the analyzed paths show an error message: “The specified path, file name, or both are too long”. Is there a way to bypass this error?
A: Paths longer than 248 characters may create issues for SecReport, as well as for many other Windows programs. You may work around this issue by mapping a network drive to a parent path of the long directory structure, or by using the MS-DOS 8.3 naming convention that can be displayed using the “dir /x” command.
Q: Does SecReport require administrative privileges?
A: SecReport needs to be installed as an administrator, but does not require administrative privileges to run. However, if UAC (User Account Control) is enabled, the operating system may prompt for administrative credentials for backward compatibility reasons.
Q: I’m planning to migrate SecReport to a different machine or upgrade my installation. How do I backup my report settings?
A: Browse to the “Program Files\Smart-X\SecReport Enterprise.Console” folder and backup all files with the extensions of *.xml, *.dat and *.license. For a Web Service installation, also backup *.xml and *.dat files from the C:\inetpub\wwwroot\SecReport.WebService\bin directory. Restore these files to their original folders after migration or upgrade.