summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2010-December/001072.html
blob: b134caa2ff7aba5b63334b48edef3f76d76bc695 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-sysadm] ldap write log
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20ldap%20write%20log&In-Reply-To=%3C1291816763.17582.41.camel%40akroma.ephaone.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001071.html">
   <LINK REL="Next"  HREF="001034.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-sysadm] ldap write log</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20ldap%20write%20log&In-Reply-To=%3C1291816763.17582.41.camel%40akroma.ephaone.org%3E"
       TITLE="[Mageia-sysadm] ldap write log">misc at zarb.org
       </A><BR>
    <I>Wed Dec  8 14:59:23 CET 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="001071.html">[Mageia-sysadm] ldap write log
</A></li>
        <LI>Next message: <A HREF="001034.html">[Mageia-sysadm] [516] use a mdv-youri-submit wrapper through sudo,	for repsys
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1072">[ date ]</a>
              <a href="thread.html#1072">[ thread ]</a>
              <a href="subject.html#1072">[ subject ]</a>
              <a href="author.html#1072">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le mardi 07 d&#233;cembre 2010 &#224; 15:05 +0100, Buchan Milne a &#233;crit :
&gt;<i> On Monday, 6 December 2010 19:26:56 Michael Scherer wrote:
</I>&gt;<i> &gt; Hi,
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; while discussing on irc, we came to the conclusion that it would be nice
</I>&gt;<i> &gt; to get some audit ( by sending mail ) when a user change group, or when
</I>&gt;<i> &gt; a user is promoted.
</I>&gt;<i> 
</I>&gt;<i> Where would we want this audit data to be stored? Only in the DSA (&quot;LDAP 
</I>&gt;<i> server&quot;)? Of course, not every single change (e.g. password change by 
</I>&gt;<i> unprivileged user) is going to be of interest. While accesslog overlay can 
</I>&gt;<i> limit what changes you want to see, I think this would prevent us for using it 
</I>&gt;<i> for delta-syncreplication.
</I>
In fact, audit may not be the proper name for the idea, as least not for
the start. If we can find a way that do not requires storage, then it
would be better.

&gt;<i> Of course, plain accesslog info is not *that* easy to audit, so we might 
</I>&gt;<i> prefer to have a view of it in CatDap (I've been looking for something to put 
</I>&gt;<i> under &quot;LDAP Admin&quot; :-)).
</I>&gt;<i> 
</I>&gt;<i> &gt; A way to do that would be to use the accesslogs overlay, with a cronjob
</I>&gt;<i> &gt; to get data from it, and to send them by mail and/or store them too, if
</I>&gt;<i> &gt; needed.
</I>&gt;<i> 
</I>&gt;<i> There are other ways, such as syncrepl consumer which evaluates changes, and 
</I>&gt;<i> could notify immediately (via any suitable medium). I have some code for such 
</I>&gt;<i> a tool, but it would need to be more configurable than it is now.
</I>
Sound good for this job.

&gt;<i> &gt; Does someone see a problem, or a better idea ?
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; Obviously, we will need to be careful about what is sent and where, for
</I>&gt;<i> &gt; privacy reason.
</I>&gt;<i> 
</I>&gt;<i> Well, I think we may want to consider two aspects:
</I>&gt;<i> -An automated process that informs relevant people of actions that may warrant 
</I>&gt;<i> further investigation (e.g. &quot;User xxx was promoted to objectClass yyy&quot;, or 
</I>&gt;<i> &quot;Member of super-privileged account sustained 100 password failures in 5 
</I>&gt;<i> minutes, and is locked out&quot;)
</I>&gt;<i> -A tool which allows searching on events in the case further investigation is 
</I>&gt;<i> warranted
</I>
For the moment, the idea is more like the changelog list of package than
to watch suspicious changes. 
Like &quot;user got promoted by admin&quot; &quot;user got added to team foo by admin2&quot;
&quot;user leaved team foo&quot;.

Ie, something quite lightweight for the moment, for better
communication.

The auditing goal is a different beast, warranting more details, more
consideration and IMHO more preparation. ( ie, be sure that we manage
the storage issue, the backup, the privacy of the access, a easy way to
audit, define what is suspicious, etc ).

-- 
Michael Scherer

</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001071.html">[Mageia-sysadm] ldap write log
</A></li>
	<LI>Next message: <A HREF="001034.html">[Mageia-sysadm] [516] use a mdv-youri-submit wrapper through sudo,	for repsys
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1072">[ date ]</a>
              <a href="thread.html#1072">[ thread ]</a>
              <a href="subject.html#1072">[ subject ]</a>
              <a href="author.html#1072">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>