Issues concerning MSAS B-1

  • Thread starter Thread starter James Baltimore
  • Start date Start date
J

James Baltimore

Anti-Spyware Developers,

I have noticed a number of minor issues concerning Beta-1
which by my perspective need to be addressed before the
RC version:

The first is that the engine is not performing correctly,
and can be an issue with Server performance. Direct
comparison to other anti-spyware applications reveals
MSAS Beta-1 to be considerably slower.

The abort function sometimes fails to comply due to some
type of delay during scanning.

The interface can in some cases request an abort choice
when choosing any link other than Help.

The ability to define which directories, subdirectories,
and/or drives to be ignored should be saved, and the
engine should not continue to scan the identified
locations during the next scan.

Keylogger definitions are not, but should be included in
the spyware definition files. I have identified illegal
access of e-mail transmission from my system to an ADSL
location, and other anti-spyware applications have
identified a Kelogger as the cause. The most likely
culprit is Probot.

Another issue which concerns me is that MSAS B-1 does not
appear to be scanning the System Restore files
accurately. After a scan I can still locate StartPage in
the System Restore directory.

If there is any additional input you require, please feel
free to contact me.

Sincerely,
James Baltimore
audiodog"at"barebonesaudio-dot-com
 
Expect to see tremendous changes in terms of UI, performance and
reliability. Right now, its not targetted for production environments
especially this particular beta 1 release. Microsoft is currently working on
an Enterprise Edition of MSAS for network environments with support for
Group Policy Editor and Central Management.
 
James - keyloggers are definitely targetted by Microsoft Antispyware. I
would think it quite likely that ProBot would be detected by Microsoft
Antispyware, but haven't tested this.
 
Back
Top