[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 88572] New: Kexi enhancement - security and auditability
From:       "D.Le Sage" <david.lesage () auroraenergy ! com ! au>
Date:       2004-09-01 1:26:43
Message-ID: 20040901012643.19142.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=88572      
           Summary: Kexi enhancement - security and auditability
           Product: kde
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: bastian kde org
        ReportedBy: david.lesage auroraenergy com au


Version:            (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs
Compiler:          GCC 
OS:                Linux

I would like Kexi to have the ability whereby a database administrator can lock \
certain tables so that only people granted access can view them.  I would also like \
the abiity to add an audit trail log, so that if changes occur to certain records and \
tracking is switched on, a text file log is produced recording the username, time and \
date and nature of the change.  Obviously, these could become huge but as text files, \
could be gzipped quite nicely.

In my current situation, I have inherited a database with a large amount of financial \
information and critical asset data for my business (a Government electrical \
utility.)  As much of our IT has been outsourced, we are locked into a cotnract \
whereby I must use Microsoft Access to change the databse link tables and not use SQL \
Server (we are entirely Microsoft-oriented, unfortunately) or even have direct access \
to our servers. 

CUrrently, many people link to this database and undertake all manner of changes, due \
to a very lax security policy I have also inherited.  As I cannot stop all of these \
supposedly business-critical updates form occurring,t eh ability to block certain \
tables from certain users would be great, as would audit trail logging.  If Kexi \
could have this ability, it would be great.

P. S. - who wants my job?!


[prev in list] [next in list] [prev in thread] [next in thread]