cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Governance
Join discussions on data governance practices, compliance, and security within the Databricks Community. Exchange strategies and insights to ensure data integrity and regulatory compliance.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Security Analysis Tool (SAT) on GCP - OSError: [Errno 5] Input/output error

GlenMacLarty
New Contributor III

I am interested to hear from anyone who has setup the Security Analysis Tool (SAT) on a GCP hosted Databricks environment.

I am in the process of getting the tool setup and I'm experiencing issues running the security_analysis_initializer notebook. The observation is that when the readBestPracticesConfigsFile() call attempts to access the CSV from the workspace location there is a file access error.

The error returned is 

 

OSError: [Errno 5] Input/output error: '/Workspace/Users/<user>/<path>/security-analysis-tool/notebooks/Utils'

This is happening when attempting to load the default best practices CSV from the workspace location. I have been able to work around this by refactoring and using a DBFS location, but I run into this same issue again when the logging utils are being referenced.

Any pointers would be greatly appreciated.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

GlenMacLarty
New Contributor III

Thanks @Retired_mod,

I have been able to get past this error through recreating the cluster with absolute barebone config. It was potentially a custom configuration (unknown at this time) which was causing this to fail. I will try and reproduce once I get some further issues sorted and provide a summary to the community to help others who may run into similar problems.

Thanks for the tips. I did actually refactor to use the dbfs location, but the issue was manifesting elsewhere in the official SAT code due to the cluster misconfiguration so resolving it was the only option to ensure I wasn't using a customised SAT setup.

View solution in original post

1 REPLY 1

GlenMacLarty
New Contributor III

Thanks @Retired_mod,

I have been able to get past this error through recreating the cluster with absolute barebone config. It was potentially a custom configuration (unknown at this time) which was causing this to fail. I will try and reproduce once I get some further issues sorted and provide a summary to the community to help others who may run into similar problems.

Thanks for the tips. I did actually refactor to use the dbfs location, but the issue was manifesting elsewhere in the official SAT code due to the cluster misconfiguration so resolving it was the only option to ensure I wasn't using a customised SAT setup.

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group