Sponsored Content
Full Discussion: Secure & Audit logs
Operating Systems Linux Red Hat Secure & Audit logs Post 302587315 by verdepollo on Wednesday 4th of January 2012 02:10:32 PM
Old 01-04-2012
I'm still not getting you fully. You want to rotate the logs every 6 months, but also on a weekly basis?

You can indeed use your current syslog and just add more logs to it; Keep in mind however that all other logs will also start to follow the same 6-month rotation rules. Mail spools for instance are prone to eat up large amounts of space when something goes wrong whith the mail daemon. The same is true for "messages" log file if it's keeping a record of debugging information.

Used space in /var depends on the size of the logs as well as the size of the filesystem. Without having a good understanding of your particular system it'd be hard to tell exactly what would be the best approach to follow in order to prevent disk saturation.

Last edited by verdepollo; 01-04-2012 at 03:19 PM..
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Security & audit

I am new to the world of Unix. As part of my understanding to have a big picture of Unix, I need to understand: 1. How to review the existing unix system or audit for the settings? 2. How do I go about fixing the holes? (4 Replies)
Discussion started by: amundra
4 Replies

2. UNIX and Linux Applications

Secure FTP Client that Logs well

Folks I am on a quest.... I am looking for a lightweight FTP client capable of FTPS and or SFTP that has good audit and logging capabilities without requiring a central server component. My platforms are Linux, Solaris, AIX, and Windows Server. The kicker is I have found things that meet the... (3 Replies)
Discussion started by: ArtF
3 Replies

3. Solaris

how to find whether audit log is secure?

How do i find if audit logs is secured inside Solaris 10? · Verify that that audit log files are secured and owned appropriately. this is the question (1 Reply)
Discussion started by: werbotim
1 Replies

4. AIX

When AIX audit start, How to set the /audit/stream.out file size ?

Dear All When I start the AIX(6100-06)audit subsystem. the log will save in /audit/stream.out (or /audit/trail), but in default when /audit/stream.out to grow up to 150MB. It will replace the original /audit/stream.out (or /audit/trail). Then the /audit/stream.out become empty and... (2 Replies)
Discussion started by: nnnnnnine
2 Replies

5. Solaris

How to view audit logs in Solaris?

Does anyone know if there is software written to view the audit logs generated by Solaris? I am referring the the logs created by auditd. It produces an unreadable log. I am familiar with auditreduce and praudit, but I am looking for something that produces a report, much like logwatch looks at the... (4 Replies)
Discussion started by: brownwrap
4 Replies

6. Solaris

Configuring 'auditd' service to not store the audit logs in /var partition

Hello all, I've configured 'audit' service to send the audit logs to a remote log server (by using syslog plugin), which is working fine. However, there is a problem. audit service also tries to write same information (but in binary format) in /var/audit path. So, Is there anyway to stop... (2 Replies)
Discussion started by: Anti_Evil
2 Replies

7. Red Hat

Comprehensive Disk & Server Logs.

Hello All, I'm using a RHEL6.4 on IBM X3850 X5 server. I want to get a comprehensive report containing disk-wise health status as well as overall server status. I see there's utility "ibm_utl_dsa_dsytd3h-9.51_portable_rhel6_x86-64.bin" which is also used to do diagnostics tasks. I'm not sure of... (1 Reply)
Discussion started by: vaibhavvsk
1 Replies

8. Solaris

How can i enable audit logs for global zone and standard zones?

HI Community, how can i configure audit logs for global zones and standard zone. i have enabled and started auditd service and it went to maintenance mode. please help me to configure that Thanks & Regards, BEn (9 Replies)
Discussion started by: bentech4u
9 Replies

9. UNIX for Beginners Questions & Answers

Grep a pattern & Email from latest logs

MyLOG: 2017/11/12 17:01:54.600 : Error: LPID: 3104680848 WRONG CRITERIA FOUND. tRealBuilder::Generate Output Required: If Ke word "WRONG CRITERIA FOUND" in latest log ( logs are regularly generating - real time) mail to us once mailed wait for 2 hours for second mail. mail subject... (3 Replies)
Discussion started by: vivekn
3 Replies

10. Solaris

Settings audit logs for different tasks. Help me!!!

Hi guys. I have to set audit logs on certain events on a solaris 10 server. While I had no problems on linux, I'm going crazy to do the same thing on solaris 10, since I don't have enough expertise on this OS . I should be able to identify these 4 different events: 1: Tracking all... (2 Replies)
Discussion started by: menofmayhem
2 Replies
NEWSYSLOG.CONF(5)					      BSD File Formats Manual						 NEWSYSLOG.CONF(5)

NAME
newsyslog.conf -- newsyslog(8) configuration file DESCRIPTION
The newsyslog.conf file is used to set log file rotation configuration for the newsyslog(8) utility. Configuration may designate that logs are rotated based on size, last rotation time, or time of day. The newsyslog.conf file can also be used to designate secure permissions to log files at rotation time. During initialization, newsyslog(8) reads a configuration file, normally /etc/newsyslog.conf, to determine which logs may potentially be rotated and archived. Each line has five mandatory fields and four optional fields, separated with whitespace. Blank lines or lines beginning with '#' are ignored. If '#' is placed in the middle of the line, the '#' character and the rest of the line after it is ignored. To prevent special meaning, the '#' character may be escaped with ''; in this case preceding '' is removed and '#' is treated as an ordinary character. The fields of the configuration file are as follows: logfile_name Name of the system log file to be archived, or the literal string ``<default>''. The special default entry will only be used if a log file name is given as a command line argument to newsyslog(8), and if that log file name is not matched by any other line in the configuration file. owner:group This optional field specifies the owner and group for the archive file. The ':' is essential regardless if the owner or group field is left blank or contains a value. The field may be numeric, or a name which is present in /etc/passwd or /etc/group. By default, log files are owned by root:admin. mode Specify the file mode of the log file and archives. count Specify the maximum number of archive files which may exist. This does not consider the current log file. size When the size of the log file reaches size in kilobytes, the log file will be trimmed as described above. If this field contains an asterisk ('*'), the log file will not be trimmed based on size. when The when field may consist of an interval, a specific time, or both. If the when field contains an asterisk ('*'), log rotation will solely depend on the contents of the size field. Otherwise, the when field consists of an optional interval in hours, usually fol- lowed by an '@'-sign and a time in restricted ISO 8601 format. Additionally, the format may also be constructed with a '$' sign along with a rotation time specification of once a day, once a week, or once a month. If a time is specified, the log file will only be trimmed if newsyslog(8) is run within one hour of the specified time. If an inter- val is specified, the log file will be trimmed if that many hours have passed since the last rotation. When both a time and an interval are specified then both conditions must be satisfied for the rotation to take place. There is no provision for the specification of a timezone. There is little point in specifying an explicit minutes or seconds compo- nent in the current implementation, since the only comparison is ``within the hour''. ISO 8601 restricted time format: The lead-in character for a restricted ISO 8601 time is an '@' sign. The particular format of the time in restricted ISO 8601 is: [[[[[cc]yy]mm]dd][T[hh[mm[ss]]]]]. Optional date fields default to the appropriate component of the current date; optional time fields default to midnight; hence if today is January 22, 1999, the following date specifications are all equivalent: '19990122T000000' '990122T000000' '0122T000000' '22T000000' 'T000000' 'T0000' 'T00' '22T' 'T' '' Day, week, and month time format: The lead-in character for day, week, and month specification is a '$' sign. The particular format of day, week, and month specifica- tion is: [Dhh], [Ww[Dhh]], and [Mdd[Dhh]], respectively. Optional time fields default to midnight. The ranges for day and hour specifications are: hh hours, range 0..23 w day of week, range 0..6, 0 = Sunday dd day of month, range 1..31, or one of the letters 'L' or 'l' to specify the last day of the month. Some examples: $D0 rotate every night at midnight (same as @T00) $D23 rotate every day at 23:00 (same as @T23) $W0D23 rotate every week on Sunday at 23:00 $W5D16 rotate every week on Friday at 16:00 $M1D0 rotate at the first day of every month at midnight (i.e., the start of the day; same as @01T00) $M5D6 rotate on every 5th day of month at 6:00 (same as @05T06) flags This optional field is made up of one or more characters that specify any special processing to be done for the log files matched by this line. The following are valid flags: B indicates that the log file is a binary file, or has some special format. Usually newsyslog(8) inserts an ASCII message into a log file during rotation. This message is used to indicate when, and sometimes why the log file was rotated. If B is specified, then that informational message will not be inserted into the log file. C indicates that the log file should be created if it does not already exist, and if the -C option was also specified on the command line. D indicates that newsyslog(8) should set the UF_NODUMP flag when creating a new version of this log file. This option would affect how the dump(8) command treats the log file when making a file system backup. G indicates that the specified logfile_name is a shell pattern, and that newsyslog(8) should archive all filenames matching that pattern using the other options on this line. See glob(3) for details on syntax and matching rules. J indicates that newsyslog(8) should attempt to save disk space by compressing the rotated log file using bzip2(1). N indicates that there is no process which needs to be signaled when this log file is rotated. U indicates that the file specified by path_to_pid_file will contain the ID for a process group instead of a process. This option also requires that the first line in that file be a negative value to distinguish it from a process ID. Z indicates that newsyslog(8) should attempt to save disk space by compressing the rotated log file using gzip(1). - a minus sign will not cause any special processing, but it can be used as a placeholder to create a flags field when you need to specify any of the following fields. path_to_pid_file This optional field specifies the file name containing a daemon's process ID or to find a group process ID if the U flag was speci- fied. If this field is present, a signal_number is sent the process ID contained in this file. If this field is not present, then a SIGHUP signal will be sent to syslogd(8), unless the N flag has been specified. This field must start with '/' in order to be recog- nized properly. signal_number This optional field specifies the signal number that will be sent to the daemon process (or to all processes in a process group, if the U flag was specified). If this field is not present, then a SIGHUP signal will be sent. SEE ALSO
bzip2(1), gzip(1), syslog(3), chown(8), newsyslog(8), syslogd(8) HISTORY
This manual page first appeared in FreeBSD 4.10. BSD
November 27, 2006 BSD
All times are GMT -4. The time now is 01:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy