Are incorrect login attempts logged in by the website or company





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}






up vote
-2
down vote

favorite












When you put in an incorrect user id and/or password , do companies/websites keep a record of that?



Like for example Joe1 had an incorrect login attempt at this time?



And if so how long do they keep record of that.






security







share|improve this question




















  • 1




    Why do you ask?
    – Joe Strazzere
    39 mins ago

















up vote
-2
down vote

favorite












When you put in an incorrect user id and/or password , do companies/websites keep a record of that?



Like for example Joe1 had an incorrect login attempt at this time?



And if so how long do they keep record of that.






security







share|improve this question




















  • 1




    Why do you ask?
    – Joe Strazzere
    39 mins ago













up vote
-2
down vote

favorite









up vote
-2
down vote

favorite











When you put in an incorrect user id and/or password , do companies/websites keep a record of that?



Like for example Joe1 had an incorrect login attempt at this time?



And if so how long do they keep record of that.






security







share|improve this question















When you put in an incorrect user id and/or password , do companies/websites keep a record of that?



Like for example Joe1 had an incorrect login attempt at this time?



And if so how long do they keep record of that.






security




security






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 39 mins ago









Kilisi

109k61244423




109k61244423










asked 48 mins ago









Steve P

21




21








  • 1




    Why do you ask?
    – Joe Strazzere
    39 mins ago














  • 1




    Why do you ask?
    – Joe Strazzere
    39 mins ago








1




1




Why do you ask?
– Joe Strazzere
39 mins ago




Why do you ask?
– Joe Strazzere
39 mins ago










1 Answer
1






active

oldest

votes

















up vote
3
down vote













This is company dependent, normal security protocols would be 'yes', time could be unlimited it's just a log file. Mine has never been stopped or archived for years. I see what username they attempted with, ip address, the timestamp and the password they tried to use. This is a very basic log. Others are more intricate.






share|improve this answer





















  • does It make it look suspicious if you keep clicking forgetting password?
    – Steve P
    35 mins ago










  • Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
    – Kilisi
    33 mins ago






  • 1




    This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
    – Nathan Cooper
    5 mins ago












  • @NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
    – Kilisi
    3 mins ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
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',
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
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f123873%2fare-incorrect-login-attempts-logged-in-by-the-website-or-company%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote













This is company dependent, normal security protocols would be 'yes', time could be unlimited it's just a log file. Mine has never been stopped or archived for years. I see what username they attempted with, ip address, the timestamp and the password they tried to use. This is a very basic log. Others are more intricate.






share|improve this answer





















  • does It make it look suspicious if you keep clicking forgetting password?
    – Steve P
    35 mins ago










  • Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
    – Kilisi
    33 mins ago






  • 1




    This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
    – Nathan Cooper
    5 mins ago












  • @NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
    – Kilisi
    3 mins ago

















up vote
3
down vote













This is company dependent, normal security protocols would be 'yes', time could be unlimited it's just a log file. Mine has never been stopped or archived for years. I see what username they attempted with, ip address, the timestamp and the password they tried to use. This is a very basic log. Others are more intricate.






share|improve this answer





















  • does It make it look suspicious if you keep clicking forgetting password?
    – Steve P
    35 mins ago










  • Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
    – Kilisi
    33 mins ago






  • 1




    This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
    – Nathan Cooper
    5 mins ago












  • @NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
    – Kilisi
    3 mins ago















up vote
3
down vote










up vote
3
down vote









This is company dependent, normal security protocols would be 'yes', time could be unlimited it's just a log file. Mine has never been stopped or archived for years. I see what username they attempted with, ip address, the timestamp and the password they tried to use. This is a very basic log. Others are more intricate.






share|improve this answer












This is company dependent, normal security protocols would be 'yes', time could be unlimited it's just a log file. Mine has never been stopped or archived for years. I see what username they attempted with, ip address, the timestamp and the password they tried to use. This is a very basic log. Others are more intricate.







share|improve this answer












share|improve this answer



share|improve this answer










answered 42 mins ago









Kilisi

109k61244423




109k61244423












  • does It make it look suspicious if you keep clicking forgetting password?
    – Steve P
    35 mins ago










  • Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
    – Kilisi
    33 mins ago






  • 1




    This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
    – Nathan Cooper
    5 mins ago












  • @NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
    – Kilisi
    3 mins ago




















  • does It make it look suspicious if you keep clicking forgetting password?
    – Steve P
    35 mins ago










  • Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
    – Kilisi
    33 mins ago






  • 1




    This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
    – Nathan Cooper
    5 mins ago












  • @NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
    – Kilisi
    3 mins ago


















does It make it look suspicious if you keep clicking forgetting password?
– Steve P
35 mins ago




does It make it look suspicious if you keep clicking forgetting password?
– Steve P
35 mins ago












Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
– Kilisi
33 mins ago




Yes it does, certainly doesn't say anything positive anyway. Not an issue if it's something you rarely log in to. But it would catch my eye if someone was persistently having the issue on a system they use all the time. Depends what it is.
– Kilisi
33 mins ago




1




1




This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
– Nathan Cooper
5 mins ago






This is a good example of how services that don't store your passwords as plain text in the obvious place still end up storing your passwords as plain text in their logs. Don't reuse passwords folks.
– Nathan Cooper
5 mins ago














@NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
– Kilisi
3 mins ago






@NathanCooper some do, some don't... mine are closed systems not publicly accessible, didn't bother getting too fancy. Some clients I set up don't store the password attempted, it's all down to the type of security you want to set up. These things are rarely done without putting a bit of thought into it. But I agree, DONT reuse passwords, it makes a single point of failure, never a good idea
– Kilisi
3 mins ago




















draft saved

draft discarded




















































Thanks for contributing an answer to The Workplace 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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f123873%2fare-incorrect-login-attempts-logged-in-by-the-website-or-company%23new-answer', 'question_page');
}
);

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







-