SX2000 maintenance logs

SX2000 maintenance logs

NewsGroups | Search | Tools
 comp.dcom.telecom.tech  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
SX2000 maintenance logs Proteus 05-24-2005
Posted by Proteus on May 24, 2005, 1:45 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


Is it possible to prevent the SYSTEM level access from generating a
maintenance log entry whenever logging on & off? If so, how, please?

I suspect we have a customer who is maliciously tampering with the database.
Fortunately he does not have the SYSTEM level password and I want to try and
catch him out with times/dates etc when he logs on and off. But I don't want
him to know there is a level above his access.

Failing that, is it possible to delete the maintenance logs without causing
problems to the system? I doubt I would be able to delete the
*.logs.maintenance file while I'm logged on anyway.

Cheers




Posted by on May 26, 2005, 2:50 pm
If you were  Registered and logged in, you could reply and use other advanced thread options



>Is it possible to prevent the SYSTEM level access from generating a
>maintenance log entry whenever logging on & off? If so, how, please?

>I suspect we have a customer who is maliciously tampering with the database.
>Fortunately he does not have the SYSTEM level password and I want to try and
>catch him out with times/dates etc when he logs on and off. But I don't want
>him to know there is a level above his access.

>Failing that, is it possible to delete the maintenance logs without causing
>problems to the system? I doubt I would be able to delete the
>*.logs.maintenance file while I'm logged on anyway.

What level is the customer logging in under? If he has the installer
password he's pretty much free to edit any form. However, MAINT21, MAINT2
and SUPERVISOR access levels can each be individually restricted as to
which forms they can and cannot access. You can go so far as to grant
either read only, read/write or NO access to whichever forms you choose.

You might want to change the PW on the installer and then give him MAINT1
priviledges with access only to the forms he actually needs. It's pretty
easy to do.





Posted by Proteus on May 26, 2005, 8:27 pm
If you were  Registered and logged in, you could reply and use other advanced thread options



>
> >Is it possible to prevent the SYSTEM level access from generating a
> >maintenance log entry whenever logging on & off? If so, how, please?
>
> >I suspect we have a customer who is maliciously tampering with the
database.
> >Fortunately he does not have the SYSTEM level password and I want to try
and
> >catch him out with times/dates etc when he logs on and off. But I don't
want
> >him to know there is a level above his access.
>
> >Failing that, is it possible to delete the maintenance logs without
causing
> >problems to the system? I doubt I would be able to delete the
> >*.logs.maintenance file while I'm logged on anyway.
>
> What level is the customer logging in under? If he has the installer
> password he's pretty much free to edit any form. However, MAINT21, MAINT2
> and SUPERVISOR access levels can each be individually restricted as to
> which forms they can and cannot access. You can go so far as to grant
> either read only, read/write or NO access to whichever forms you choose.
>
> You might want to change the PW on the installer and then give him MAINT1
> priviledges with access only to the forms he actually needs. It's pretty
> easy to do.
>
>
Yeah thanks for that suggestion, but I want to catch him out without
necessarily alerting him to the fact that someone else may have a higher
level access than he does. If he sees another user logging in & out in the
maint logs, he will just ask me who is SYSTEM and what is the password &
what does it do etc etc....
Each time he buggers something up, I just correct it, then restrict
installer access to that particular form.






Posted by on May 26, 2005, 8:31 pm
If you were  Registered and logged in, you could reply and use other advanced thread options





>Yeah thanks for that suggestion, but I want to catch him out without
>necessarily alerting him to the fact that someone else may have a higher
>level access than he does. If he sees another user logging in & out in the
>maint logs, he will just ask me who is SYSTEM and what is the password &
>what does it do etc etc....
>Each time he buggers something up, I just correct it, then restrict
>installer access to that particular form.

Didn't realize you could restrict the "installer" from any form. Thot that
was more the purview of MAINT1/MAINT2/SUPERVISOR access levels. Ya learn
sump'n every day it seems. Shame session logging won't capture CDE.

Here's a trick... if it's non-redundant, i.e., a microlight, leave him a
little reminder you were there with a bulletin banner on the bottom of his
screen. Sample syntax: (minus the quotes)
"EC *** NOTICE: ALL SYSTEM PROGRAMMING ACTIVITY IS BEING LOGGED ***"

"EC" is sometimes a handy little command ;-)





Posted by Ian on May 27, 2005, 8:54 am
If you were  Registered and logged in, you could reply and use other advanced thread options



>
>
>
> >Yeah thanks for that suggestion, but I want to catch him out without
> >necessarily alerting him to the fact that someone else may have a higher
> >level access than he does. If he sees another user logging in & out in
the
> >maint logs, he will just ask me who is SYSTEM and what is the password &
> >what does it do etc etc....
> >Each time he buggers something up, I just correct it, then restrict
> >installer access to that particular form.
>
> Didn't realize you could restrict the "installer" from any form. Thot that
> was more the purview of MAINT1/MAINT2/SUPERVISOR access levels. Ya learn
> sump'n every day it seems. Shame session logging won't capture CDE.
>
> Here's a trick... if it's non-redundant, i.e., a microlight, leave him a
> little reminder you were there with a bulletin banner on the bottom of his
> screen. Sample syntax: (minus the quotes)
> "EC *** NOTICE: ALL SYSTEM PROGRAMMING ACTIVITY IS BEING LOGGED ***"
>
> "EC" is sometimes a handy little command ;-)
>
Hi

Well I know I cant alter what installer can access on my Lab system.

Ian




Similar ThreadsPosted
NEC Electra Elite call logs November 29, 2007, 2:53 pm
TVA-50 Voicemail software (TVA Maintenance Console) September 18, 2008, 8:06 pm
SX2000 CCS trace April 13, 2005, 6:54 pm
Another odd SX2000 Problem July 11, 2005, 2:00 am
sx2000 question August 22, 2005, 9:35 pm
SX2000 lost password June 6, 2005, 11:34 am
sx2000 pri sync issue June 24, 2005, 6:58 pm
yet another sx2000 question re ons class June 27, 2005, 8:40 am
SX2000 to SX200 T1 Tie Line July 10, 2005, 11:55 pm
mitel sx2000 lw29 TBCT March 8, 2005, 3:03 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map