Date: Tue, 24 Oct 2023 19:59:46 +0000 From: void <void@f-m.fm> To: freebsd-security@freebsd.org Subject: Re: securelevel 1 Message-ID: <0adf3c6f-d739-4e40-9504-8633d11ebf1c@app.fastmail.com> In-Reply-To: <20231024174540.1936912D@slippy.cwsent.com> References: <ZTeaGFZjvcsKfbOW@int21h> <6638DADD-FCDB-492C-B1E8-441C6622038B@FreeBSD.org> <663fd243-94ec-40c1-ac66-ca8e3d5f278d@quip.cz> <35f733cc-a6c2-46a4-b564-b1ef87893fc5@app.fastmail.com> <20231024174540.1936912D@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Oct 2023, at 17:45, Cy Schubert wrote: > What a lot of large enterprises do is send logs off machine. A *.* log to > @IP or an agent does the same thing. The remote logging server also has > software to allow one to search the logs for a machine or multiple machines > allowing one to correlate messages across the network. > > For server admins logging into each server individually, correlating logs > can be time consuming and a little challenging as one must keep a lot of > information in mind when working with multiple machines. But with logs sent > to a single server a person can use software designed to correlate logs. Yes, I'm considering that (remote logging) too. That's probably the best solution even with only a couple of machines. Thanks everyone
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0adf3c6f-d739-4e40-9504-8633d11ebf1c>