AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Symantec endpoint protection 1510/30/2023 ![]() ![]() To make the frequency tables a reasonable size, I have lumped all non-alphabetic characters together into the same group. ![]() ![]() ![]() The number of bits listed for entropy is an estimate based on letter pair combinations in the English language.< 28 bits = Very Weak might keep out family membersĢ8 - 35 bits = Weak should keep out most people, often good for desktop login passwordsģ6 - 59 bits = Reasonable fairly secure passwords for network and company passwordsĦ0 - 127 bits = Strong can be good for guarding financial information Password strength is determined with this chart, which might be a bit of a stretch for a non-critical password:.Warnings are shown if your password is very short (4 or less characters) or if it is short (less than 8 characters).Warnings are shown if you enter a common password.In the example below, I tested an easy password : " password " and The Password Checker ( Strength Test - ) gives an estimation about how strong is this password in terms of strenght, entropy and charset size. Invoke-Command -Session $session -ScriptBlock īy adding in a semicolon we can of course add a second line to our ScriptBlock and make the process a little more automated.I found another good resource to to check how is safe or weak a password. The challenge i had was that on several clients it seemed Symantec had a different IdentifyingNumber (IN), which is the GUID used by Windows to identify the product.Īs there were only 7 client machines i did a lot more of this manually than perhaps i needed to.įirstly i found the right IdentifyingNumbe r from each PC. I already had the machines on the network configured for PowerShell Remoting, so connecting to them was not a challenge. There are various ways of course to execute a command on a remote machine, you can use PSTools’, PSExec for example, but i prefer to use PowerShell where i can. I did a lot of searching around for a reliable solution, most of which came back to using MSIEXEC from a command line. It was a small SEPM deployment, only 7 clients and a server but i was surprised to be reminded that SEPM has no ‘uninstall’ tool from their console. Finally moving my last client from Symantec SEPM to Trend Micros WFBS Hosted platform. ![]()
0 Comments
Read More
Leave a Reply. |