Browse by Tags
All Tags »
development »
service hardeni... »
security (RSS)
( This is part 5 of our series of posts on service hardening .) Last but not least a service can be (and should be) configured to have network restrictions with what is called the "Windows Service Hardening" rules in the Windows SDK (we'll call those
Read More...
( This is part 4 of our series of posts on service hardening. ) A service can be configured to be write-restricted, in addition to having a per-service SID. To do so, you specify a SID type of "Restricted" when configuring your service (see our previous
Read More...
(This is part 3 of our series of posts on service hardening.) Under Windows Vista/Longhorn Server, your service can now have its own SID (Security Identifier), which you can then use in ACLs to protect your service resources. You configure your service
Read More...
This is part 2 of our series of posts on service hardening. "Need to have" and least privilege principle Executing with least privilege is a good practice of computer security. As with the "need to know" principle for information access, there should
Read More...
You may have heard that built-in services in Windows Vista were specifically hardened by Microsoft engineers during its development process. You might be wondering what that really means, how it works and, if you are a developer, how to harden your own
Read More...
