kwbMitel said:
If a user does not want to properly secure their mailbox then nothing you or I can do will prevent unauthorised access.
To stand by idly with the notion that [0-9]{6} is secure, would be irresponsible of anyone. In regards to the user, this is why IT exists, and why IT Security professionals are high in demand. Unfortunately, we have to think for the user (even the "brightest" of them).
For example, let's say a VM is setup with a default password. They change it and forget it. They ask IT who reset its. Rinse and repeat a few times. The user is going to naturally think IT is thinking they are the most forgetful person ever. To prevent them from having to ask IT again, they make their password simple (123456). They've solved their problem, and created another one, which they aren't aware of. Additionally, a large staff can easily inundate IT personnel with these simple requests.
kwbMitel said:
Nobody is going to try and crack a mailbox to listen to messages.
The very reason I posed my question was because this is not true. As you know through helping me on another thread, we have DIDs. Those DIDs have related VM boxes. If you were to change my VM box, every customer that reaches voice mail will hear what you've recorded. I doubt it's necessary to explain why this is a problem.
kwbMitel said:
It sounds to me like you are over thinking the issue.
I wouldn't say I am. I may be over thinking this response, but by providing short message it didn't seem to illustrate the importance of resolve this issue. From an ISS standpoint, we should only grant access or privileges to those privy of the information. Additionally, we should minimize risks where possible. So, are you saying there is absolutely no way to prevent someone from accessing menu options when they reach a voice mail box? The system has to know whether or not a call came into a switch or generated internally.