Secunia SmallBusiness
Overview
Advisories
Research
Forums
Create Profile
Our Commitment
All Threads
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: Can't get CSI to work

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
CSI

This thread has been marked as locked.
mvdm1812 Can't get CSI to work
Member 28th Jun, 2012 21:58
Ranking: 0
Posts: 1
User Since: 28th Jun, 2012
System Score: N/A
Location: NL
Hi all.
In our company we are trying to test CSI, but so far we don't succeed.
We built a new wsus 3 server and installed CSI on it.

CSI connects to WSUS, but we couldn't create the active directory policy. However, we created our own policy that point the pc's to our new wsus server.
My pc uses the new policy and the pc shows up in wsus. We created a package for an application (Adobe reader, if I remember correctly) that needed an update on my pc. We approved it to the wsus group my pc is in. Should the update appear in wsus? It's not there and it doesn't appear on my pc.
Scanning the pc from the CSI console doesn't work either, only by running CSIA -c it connects to secunia and shows the results on our CSI server.

So, long story short : CSI does not distribute packages to wsus and CSI fails when trying to scan my pc.
What are we doing wrong?

O.Marin RE: Can't get CSI to work
Secunia Official 29th Jun, 2012 15:26
Score: 25
Posts: 113
User Since: 4th Aug 2011
System Score: N/A
Location: Copenhagen, DK
Hi,

Thank you for your post.

From what I understand you have a few questions.

First one: you are not able to see the 3rd party updates in WSUS. This is a normal behavior because the WSUS is not equipped to handle 3rd party packages. You can view the published packages published with Secunia CSI under Patch -> Available. Here you can approve them to specific groups.

Second question: You tried to run a scan and that scan failed. If you are using remote scan (Quick Scan, Scan Groups, CSI Agent in Network Appliance Mode) then you need to have some requirements in place:
Scanning using remote login (Agent-less):
• Administrative privileges
• Microsoft Windows XP Service Pack 3, 2003, 2008, Vista, and 7
• Windows Update Agent 2.0
• Standard Windows services/ports:
o Workstation and Server Service
o Remote Registry Service
o File and Print Sharing
o COM+
o Ports 139/tcp and 445/tcp open inbound

You can also use the CSI Agent in Single Host Mode to run scans (I think you already use the binary with the –c option).

For more information you can use our online resources:
CSI 5.0 Technical User Manual
http://secunia.com/resources/product_sheets/
CSI 5.0 Videos
http://secunia.com/resources/videos/

Let me know if you need more information on the solution or if you experience any other issues,


--
Kind Regards,

Oana Marin
Solution Specialist

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Factsheets
Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2013 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability