Administering SSIS: Security-related SSIS Questions

I credit my friend and brother, Chris Yates (Blog | @YatesSQL), for inspiring me to write this post with his (excellent) post: Reports in SSIS.

If I had a nickel for each time I’ve been asked, “What permissions are required for SSIS?” I would have a lot of nickels.

It’s a fair question with an unfair answer, “It depends.”

“It Depends on What?”

Here are some considerations:

SSIS Execution
- Who has permission to execute SSIS packages?
SSIS Administration
- Who has permission to deploy, delete, import, and export SSIS packages?
- Who has permissions to view SSIS Catalog reports?
SSIS Authentication
- To which databases will SSIS packages need to connect?
SSIS Authorization
- What functions will SSIS packages need to exercise once connected to resources?
SSIS Encryption
- Is there a reason to encrypt the logic contained in the SSIS package?
SSIS Obfuscation
- Does the SSIS package contain proprietary logic or intellectual property (IP)?
SSIS Maintenance and Revision
- Who is authorized to update SSIS packages?
SSIS Testing
- What is the process for testing SSIS packages?
- Who performs SSIS package tests?

These are some, but not all, considerations surrounding enterprise Data Integration Lifecycle Management (DILM) DevOps. A more detailed version of this list may be found in my post DevOps, Data Integration Lifecycle Management (DILM), and SSIS Security over on the Linchpin People Blog, which includes a link to download the full checklist in Word format.

:{>

Andy Leonard

Christian, husband, dad, grandpa, Data Philosopher, Data Engineer, Azure Data Factory, SSIS guy, and farmer. I was cloud before cloud was cool. :{>