|
|
|
In This Issue:
|
|
|
|
InterSpect
- The Internal Security Gateway
|
|
|
|
New
Early Availability Products
|
|
|

|
SDK
Update
|
|
|

|
Log
Changes and LEA Update
|
|
|
|
ELA
Behavior Changes
|
|

|
CPRA
and Provider-1
|
|

|
Check
Point User Center Accounts
|
|

|
Miscellaneous
|
|
|
|
|
|
InterSpect
- The Internal Security Gateway
We recently announced our
latest product: InterSpect - The Internal Security Gateway.
InterSpect blocks the spread of
worms and attacks inside the network. It offers intelligent
security and proactively defends against vulnerabilities.
InterSpect segments the network into security zones, minimizing
unauthorized access - intentional and unintentional.
Click
here to learn more
Currently OPSEC API's are not
supported in InterSpect. We do plan to support OPSEC
integration points such as SAM and LEA in an upcoming enhanced
release (Q2 2004).
|
|
|
New Early Availability
Products
We have released three new products for the Early Availability
program:
1. SecureClient for PocketPC 2003
2. SecuRemote/SecureClient NG AI (Known as Quebec & Simplified
Quebec)
3. NG AI (R55) for Red Hat Enterprise Linux 3.0
If you would like to participate in
the program visit our web site and register.
http://www.checkpoint.com/eap/index.html
|
|
|
SDK
Update
The OPSEC SDK libraries can be compiled on
Microsoft .Net
and this is now supported by Check Point. Check Point does not compile
the OPSEC SDK libraries with .Net but with VC++ 6.0; however, these
libraries are .Net compatible.
Note: When compiling 'debug static' the
following warnings can be ignored:
"warning LNK4099: PDB 'opsec.pdb' was not found with 'd:\lib\debug.static\opsec.lib'
or at 'd:\Debug\opsec.pdb'; linking object as if no debug info"
This happens with other products for example in http://support.microsoft.com/default.aspx?scid=kb;EN-US;818344
Microsoft suggests downloading the pdb's but offers an
alternative to allow this warning (see BUILD_ALLOW_LINKER_WARNINGS).
|
|
Log
Changes and LEA Update
LEA
partners reporting on Audit logs should use the operation ID
rather than the operation string to identify the operation.
The ID is an identifier for a type of operation.
The Operation may change from one release to the next, but
the Operation Number will stay the same.
For example consider the following audit log entry.
loc=1266
filename=fw.adtlog
.....
product=SmartView Tracker
Operation=Log In
Administrator=admin
......
Operation Number=7
In
FP3 the Operation string was “Logged In”
In later versions this was changed to “Log In”, but the
Operation Number is 7 in all versions.
For a complete list of Audit Log fields see the page Program
Design Considerations for LEA Client Certifications at the LEA
API portal
|
|
ELA
Behavior Changes
When a firewall's disk space is
full the log server will stop writing log records to the disk. In a
situation like this logs sent by ELA clients are lost.
Integration between the log server and the ELA server will be
changed in the next release - when the system
can't handle logs the ELA connections will be closed.
ELA
clients should have a mechanism to resume their sessions with the
ELA server and should queue their data so logs can be written when
the session is re-established.
|
|
|
CPRA
and Provider-1
Two
new issues have been found with CPRA (Check Point Roaming
Administrator)
and Provider-1. These issues prevent users from using CPRA in
Provider-1 environments.
To learn more about these issues and how to resolve them please
follow these SecureKnowledge articles: sk24324 and
sk24450
|
|
Check
Point User Center Accounts
All
OPSEC partners are being given enhanced account access to the User
Center. This enhancement will allow access to downloads and
other valuable partner information. New account credentials
and instructions on using it will be set to the primary contacts for
each partner. If you have recently made changes in your company
please use the following link to send us the updated contact name,
email and street address information so we can send the credentials
to the correct person. http://www.opsec.com/contact.html
|
|
Miscellaneous
SecurePlatform
and PnP Bios
An
issue was found with SecurePlatform running on machines running PnP
Bios.
The problem lies in the PnP BIOS and in the kernel
PnP handling. This issue will be fixed in the SecurePlatform version based on RHEL
3.0 (Expected to be released in Q2 2004).
For more information read SecureKnowledge solution sk22230.
Submitting RFEs
It is possible to submit RFEs (Request For Enhancement)
through the web. The RFEs can be for Check Point products and Check
Point APIs as well.
If you have any enhancement requests please take the time to submit
an RFE as we are currently planning the next release of our SDK and
have very few partner enhancement requests.
http://www.checkpoint.com/jsp/rfe/rfe.jsp
Webcasts
The Webcast archive is a good place to find important information
regarding OPSEC initiatives and programs. Three new webcasts have recently
been
uploaded (Debugging NG, SmartUpdate and CPRA)
http://www.checkpoint.com/opsecpartners/marketing/resources/replay_signup.html
|
|
For further questions please contact OPSEC
|