issPolicy Release Information
issPolicy v1.01
Release Date:
Release Information:
Supported Policies:
- RealSecure Network Sensor 7.0 (confirmed/tested)
- Proventia G-Series Inline Appliance 8.0 (confirmed/tested)
- Proventia A-Series Appliance (confirmed/tested)
Supported Operating Systems:
- UNIX/POSIX (confirmed/tested: Red Hat Linux 8.0)
- Win32 (confirmed/tested: Windows 2000, Windows XP, Windows Server 2003)
Supported Features:
- Automatically detects whether policy type is a RealSecure Network Sensor or Proventia Inline Appliance policy, and generates the HTML accordingly
- Extracts Signatures, IP Filters, and Event Filters from the RealSecure Network Sensor or Proventia Inline Appliance policy
- Contains various options for a tailored HTML Policy file to be created:
- Whether Signature is enabled or disabled
- Based on Signature Priority (High, Medium, low)
- Whether DROP is enabled (Only on Proventia Inline Appliance Policies)
- Based on DROP Options (ConnectionWithReset, Connection, Packet) (Only on Proventia Inline Appliance Policies)
- Whether DYNAMICBLOCK is enabled (Only on Proventia Inline Appliance Policies)
- Based on DYNAMICBLOCK Options (IsolateTrojan, BlockWorm, BlockIntruder) (Only on Proventia Inline Appliance Policies)
- Whether IP filter is enabled or disabled
- Whether Event Filter is enabled or disabled
Known Issues:
- [#001] - [11-Nov-2004] Formatting Issue in IP Filters Table
- Description: A formatting issue in the HTML generation subroutine causes the "Filter Description" table cell to be blank when no Filter Description is given in the policy file.
- Fix Information: This issue will be fixed in the upcoming issPolicy v1.02 release. The "Filter Description" table cell will now indicate "n/a" when no Filter Description is given in the policy file.
- Temporary Workaround: Change "issPolicy" line #766 from print HTMLPOLICY "<td>$ip_filters{$filtername}->[1]</td>"; to print HTMLPOLICY "<td>".($ip_filters{$filtername}->[1]?$ip_filters{$filtername}->[1]:"n/a")."</td>";
- Acknowledgements: Thanks to Sergey V. Soldatov for pointing out this issue and providing the workaround.
Resolved Issues: