<div>
Or can you think of any valid reason why a share with the applications files would be accessible with read write execute permissions to the builtin\users group?
</div>


<div>
I thought you could only delete with full access not read write or execute.
</div>


<div>
No, modify permissions are enough or write perms.
</div>


<div>
<div class="content wysiwyg-content">
We have an application server with a share dedicated to the apps files. this application has a lot of &quot;attachments&quot; so stuff like PDFs, jpg images etc are stored here. we have just reviewed the ACL for the share, share - everyone F, directory has many groups but one that causes concern is builtin\users RWX.<br />
<br />
Its a windows 2003 server, the docs arent sensitive/confidential, but what could rwx allow someone with malicious intentions to do to those files? Is there a risk?
</div>
</div>


We have an application server with a share dedicated to the apps files. this application has a lot of "attachments" so stuff like PDFs, jpg images etc are stored here. we have just reviewed the ACL for the share, share - everyone F, directory has many groups but one that causes concern is builtin\users RWX.

Its a windows 2003 server, the docs arent sensitive/confidential, but what could rwx allow someone with malicious intentions to do to those files? Is there a risk?

Or can you think of any valid reason why a share with the applications files would be accessible with read write execute permissions to the builtin\users group?

I thought you could only delete with full access not read write or execute.

No, modify permissions are enough or write perms.

app server acl concern

We have an application server with a share dedicated to the apps files. this application has a lot of &quot;attachments&quot; so stuff like PDFs, jpg images etc are stored here. we have just reviewed the ACL for the share, share - everyone F, directory has many groups but one that causes concern is builtin\users RWX.

Its a windows 2003 server, the docs arent sensitive/confidential, but what could rwx allow someone with malicious intentions to do to those files? Is there a risk?

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Operating system security (OS security) is the process of ensuring OS integrity, confidentiality and availability. OS security refers to specified steps or measures used to protect the OS from threats, viruses, worms, malware or remote hacker intrusions. OS security encompasses all preventive-control techniques, which safeguard any computer assets capable of being stolen, edited or deleted if OS security is compromised, including authentication, passwords and threats to systems and programs.