IDS Policy manager Config

Procedure for Deployment of IDS Policy Manager for Centrally managing Snort sensor.

1). Set the Update locations of the policy/rule file

2). Create Policy for the IDS Sensors.below screen shows 2 Snort IDS Policies are created for managing 2 different Sensors.Intialize the Created Policy with the Base Config file Snort.conf and the latest downloaded rules tar file.

3). 2 IDS Sensors are created as shown below. Assign the created policy to this newly created IDS Sensor.

Separate Policies are assigned for each Sensors.

Same Policy is assigned for each Sensors.

After this upload settings must be configured to upload the latest rules/snort.conf and for this FTP port 21 must be enabled from this central server to the IDS Sensor. and DOS script is also required locally to manage  the stop/start of the sensor. 

Once the policies are updated successfully the Snort IDS Sensor needs to be restarted. 

WebSphere Commerce Server - Softwares Summary

Softwares Summary for WebSphere Commerce Server

1).Database Server Oracle 9.2.0.7.0 OR 10g
2).WCS ND 6.0.25
3).WCS Commerece Installer
4).6.0.1.3 FixPack Updator
5).FixPack-1
6).Feature Pack-1
7).6.0.1.4 Update Installer
8).FixPack-2
9).Appserver Updator from 6.0.2.5 to 6.0.2.15
10).Feature Pack -2

WebSphere Commerce Server 6.0 IBM Gift Center For Consumer Direct Store

IBM Gift Center for WebSphere Commerce, an optional feature, can be installed only on WebSphere Commerce Enterprise or WebSphere Commerce Professional, not WebSphere Commerce Express.and for this we need to publish the basic sar files like ConsumerDirect starter store.
http://hostname/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp


Download and save the GiftCenterConsumerDirect.sar file to the sar directory but before that GiftCenter feature must be enable and it can be done by running config_ant.bat as shown below.

config_ant.bat -buildfile C:\IBM\WebSphere\CommerceServer60\components\GiftCenter\xml\enableGiftCenterForServer.xml -DinstanceName=wcs -DfeatureName=GiftCenter -DdbUserPassword=Password

Once this is Done successfully then Download GiftCenterConsumerDirect.sar.zip from the IBM WebSite and Rename it to GiftCenterConsumerDirect.sar and place this under C:\IBM\WebSphere\CommerceServer60\instances\wcs\sar
Now publish the above sar as shown below.
Before Publishing Read the Above instruction carefully and then go ahead.

Install SSL Certificate on IBM Http Server

Before installing the SSL certificate, install both of these CA certificates into your key store. Follow the instructions in 'Storing a CA certificate' below.

If the authority who issues the SSL certificate is not a trusted CA in the key database, you must first store the CA certificate and designate the CA as a trusted CA. Then you can import the CA-signed SSL certificate into the key database. You cannot import a CA-signed SSL certificate from a CA who is not a trusted CA in the key database. For instructions see 'Storing a CA certificate' below.

Storing a CA Certificate:
1. Enter IKEYMAN on a command line on UNIX, or start the Key Management utility in the IBM HTTP Server folder on Windows.
2. Select Key Database File from the main User Interface, select Open.
3. In the Open dialog box, select your key database name. Click OK.
4. In the Password Prompt dialog box, enter your password and click OK.
5. Select Signer Certificates in the Key Database content frame, click the Add button.
6. In the Add CA Certificate from a File dialog box, select the certificate to add or use the Browse option to locate the certificate. Click OK.
7. In the Label dialog box, enter a label name and click OK.

Import the CA-signed SSL certificate into a key database:
1. Enter IKEYMAN on a command line on UNIX, or start the Key Management utility in the IBM HTTP Server folder on Windows.
2. Select Key Database File from the main User Interface, select Open.
3. In the Open dialog box, select your key database name. Click OK.
4. In the Password Prompt dialog box, enter your password, click OK.
5. Select Personal Certificates in the Key Database content frame and then click the Receive button.
6. In the Receive Certificate from a File dialog box, select the certificate file. Click OK.

Snort is not logging data to Database while running as Service.

The very important point in the troubleshooting of snort is always prefer to start it with the command line parameters b'cos  when you are starting it with the command lines it will display the complete trace of the commands in which we can figure out like the Ethernet Details if more then 1 ethernet cards are available on the server.

Snort as service is pointing a particular Ethernet and when u are explicitly defining in start commands you may be giving a different Ethernet details so, this is the root cause that why your snort is not logging into the database when running snort as windows/linux service

this can be verified by using the comand line params as shown below and try to run the snort also thro' the service and findout the difference.in my case the correct interface id is 1 and this can be verified by using below commands.

Check available Ethernet Cards
snort -W

Start snort in Verbose logging mode
snort -v -i1 -c D:\snort\etc\snort.conf -l D:\snort\log -K ascii

Installing / Uninstalling Snort as windows service
snort /SERVICE /INSTALL  -i1 -c D:\snort\etc\snort.conf -l D:\snort\log -K ascii

Download Documents

Configuring Microsoft Internet Information Services (IIS) with Apache Tomcat Server 


Configuring IIS with Multiple Tomcat Instances Running on the Same Server



Configuring Microsoft Internet Information Services (IIS) with IBM WebSphere 


Configuring SSL in Tomcat, WebSphere, Weblogic



Configure IHS 6.1 with SSL and WebSphere Application Server 6.1


Configuring Microsoft Internet Information Services (IIS) with Apache Tomcat Server 

MySQL DB Connection Check Perl Script

MySQL Database Backup Scheduler. 

Snort Database Cleanup Perl Script 

WebSphere WSADMIN CMD Usage

WebSphere Console Security Implementation

access Link  was http://localhost:9060/ibm/console

Enabling Global Security for WAS IBM Console

Before this copy of these files are taken sothat we can revert back.

select GlobalSecurity
goto LocalOS Tab enter valid system user/pass and save will change the foll file
cells / wwwCell01 / security.xml

SuccessMessage:-
The settings on this panel are not validated until this registry is selected as the Active user registry on the Global Security panel and security is enabled.

Still not asking for the Password
hence goto general tab of global security and check Enable Global Security and with that Enforce Java2 security is by default get checked.
Active User Registry must be local OS

Error Note:-The Lightweight Third Party Authentication (LTPA) password is not set. Validation failed.
hence password this also set as same as local os Password Administrator/Password
Changes Done to :- cells / wwwCell01 / security.xml

After All these  Changes u will hav to Restart the DManager for the changes to take effect.

Now after Enabling the Security the Access Link is

https://localhost:9043/ibm/console/logon.jsp

Tested all the activity like Server 1 Started ok and working fine.

MSSQL Mixed Mode Authentication Enable MODE

The best way to enable is to set this at the time of installation, the other way is to modify the registry for the same.

For SQL Server 2005 Express Edition, there is not GUI tool available to configure the server. You need to go it manually. The first step is to change the login-mode.

Open registry editor and go to HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer
On the right, look for an entry named LoginMode. The default value, when installed is 1. Update it to 2.

The next step is to restart the service and login.