Freeze Linux when log is full
Is it possible to configure a Linux server to stop all operations when it cannot create logs, similar to the security policy in Windows called "Audit: Shut down system immediately if unable to log security audits"?
To goal would be to prevent a server from doing anything if it cannot log what it is doing. To prevent an attacker from filling the disk, or otherwise preventing the log from being written, and then carry on malicious operations from that server.
rhel security logs audit
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
add a comment |
Is it possible to configure a Linux server to stop all operations when it cannot create logs, similar to the security policy in Windows called "Audit: Shut down system immediately if unable to log security audits"?
To goal would be to prevent a server from doing anything if it cannot log what it is doing. To prevent an attacker from filling the disk, or otherwise preventing the log from being written, and then carry on malicious operations from that server.
rhel security logs audit
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data usingFILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi
– Atul
Jan 31 at 16:06
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46
add a comment |
Is it possible to configure a Linux server to stop all operations when it cannot create logs, similar to the security policy in Windows called "Audit: Shut down system immediately if unable to log security audits"?
To goal would be to prevent a server from doing anything if it cannot log what it is doing. To prevent an attacker from filling the disk, or otherwise preventing the log from being written, and then carry on malicious operations from that server.
rhel security logs audit
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
Is it possible to configure a Linux server to stop all operations when it cannot create logs, similar to the security policy in Windows called "Audit: Shut down system immediately if unable to log security audits"?
To goal would be to prevent a server from doing anything if it cannot log what it is doing. To prevent an attacker from filling the disk, or otherwise preventing the log from being written, and then carry on malicious operations from that server.
rhel security logs audit
rhel security logs audit
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
asked Jan 31 at 15:20
Christoffer ReijerChristoffer Reijer
14817
14817
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data usingFILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi
– Atul
Jan 31 at 16:06
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46
add a comment |
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data usingFILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi
– Atul
Jan 31 at 16:06
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data using
FILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi– Atul
Jan 31 at 16:06
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data using
FILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi– Atul
Jan 31 at 16:06
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497952%2ffreeze-linux-when-log-is-full%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497952%2ffreeze-linux-when-log-is-full%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
By stop all operations, what exactly you mean ?
– Atul
Jan 31 at 16:03
How about checking if you are able to write to a file and "stop" the operations if you are not able to do so ? Creating a log file and checking the data using
FILE=<your log file > if [ -w "$FILE" ] then echo "Able to write to the logfile, continuing operations" else echo "Not able to log to the logfile" fi– Atul
Jan 31 at 16:06
Something similar to docs.microsoft.com/en-us/windows/security/threat-protection/…. You cannot login, no service is responding. All you can do is logon as admin and archive+clear the logs.
– Christoffer Reijer
Jan 31 at 20:44
I am looking for something robust, that would be difficult for the attacker to circumvent/disable.
– Christoffer Reijer
Jan 31 at 20:46