Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum PW Local Working Directory and DFARS 252.204-7012 and NIST SP 800-171 Requirements
    • Sign In

    • State Not Answered
    • Replies 1 reply
    • Subscribers 61 subscribers
    • Views 895 views
    • Users 0 members are here

    PW Local Working Directory and DFARS 252.204-7012 and NIST SP 800-171 Requirements

    Gail Heitland
    Offline Gail Heitland over 6 years ago

    Our current local working directory is set up so all users have a common name associated with their working directory.  It is set up outside of their User Profiles.  It is configured to  "Leave local copy on Check In". 

    As we move forward with implementing the above Federal Regs on Cyber security, our plans include encrypting all  employees hard drives.  However we have an internal disagreement  about how to implement storage isolation requirements in regards to a user's local working directory.  I thought encrypting all employees' hard drive would satisfy the storage isolation requirements for the local working directory.

    Options considered include configuring  a user's local working directory so that PW does not leave a local copy on Check In.  However, that will significantly affect the performance in PW as delta file transfer would no longer be applicable.   

    We also are  considering  moving the users local working directory to  inside of their User Profile.  If we do this,  we would no longer have a common name associated with a user's working directory. That would prevent certain design tools not integrated with PW from working inside of PW.    Any design application that creates or links external files that are internally configured to point to where the main file is location would no longer work inside of PW.  Having a "common" path allowed these design application to work inside of PW, no matter who created the linked files.

    I'm hoping to get an understanding how  other organizations are  addressing the Federal  "storage isolation" requirements as it pertains to the PW local working directory?     Are you limiting access to a workstation so that only the employee assigned to the PC has authorization to use it? 

    Responses and suggestions would be greatly appreciated!

    • Sign in to reply
    • Cancel
    Parents
    • Kevin van Haaren
      0 Offline Kevin van Haaren Thu, Sep 7 2017 1:46 PM

      We haven't had to do storage isolation yet but I did want to warn you about one issue we've run into when using the User Profile for the working directory.

      This probably won't affect your internal users but if you have outside people connecting in then it will most likely affect them: if in a working directory you use the $user.name$ variable that variable is the PROJECTWISE username and NOT the system username! This means if your projectwise user name and and system user name are not exactly the same the working directly will most likely point to the wrong location.

      One of the companies we work with uses:

      c:\users\$user.name$\pwdir

      and since their internal usernames don't match ours all our user's working directories are in user folders they don't (initially) have permission to and we have to set the permissions manually for each user.

      I wish Bentley allowed environment variables in the working directory.

      %LocalAppData%\Bentley\workdir would work so much better.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Kevin van Haaren
      0 Offline Kevin van Haaren Thu, Sep 7 2017 1:46 PM

      We haven't had to do storage isolation yet but I did want to warn you about one issue we've run into when using the User Profile for the working directory.

      This probably won't affect your internal users but if you have outside people connecting in then it will most likely affect them: if in a working directory you use the $user.name$ variable that variable is the PROJECTWISE username and NOT the system username! This means if your projectwise user name and and system user name are not exactly the same the working directly will most likely point to the wrong location.

      One of the companies we work with uses:

      c:\users\$user.name$\pwdir

      and since their internal usernames don't match ours all our user's working directories are in user folders they don't (initially) have permission to and we have to set the permissions manually for each user.

      I wish Bentley allowed environment variables in the working directory.

      %LocalAppData%\Bentley\workdir would work so much better.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Children
    No Data

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies