How can default user account become a security problem?
What will be an ideal response?
Default user accounts-such as the "guest" user on Windows servers, or default users on applications that are later installed on the server-can create vulnerabilities, especially if they are forgotten by the system administrators. These accounts should be deactivated or deleted if they are not being used.?Another way that default user accounts can be a problem is in situations where administrators set up all new users with the same password. In most cases this kind of practice is harmless, and makes life easier, but what if there are users set up who never log in and change their default password? Network protocol analyzers can return to an attacker the list of users who have never logged in. This can lead to a huge vulnerabilities in the system.
You might also like to view...
Can message confidentiality and message integrity protection be applied to the same message? Why or why not?
What will be an ideal response?
When writing an event-handling method in a GUI application, what should you consider about a variable's scope?
What will be an ideal response?