Thanks for the link.

My inexperience may show here with my questions/responses but in response to the options presented in that kb article:

I am not really sure how the proxy would work in my situation. I have a package, that while I created it on another machine, currently has the same CreatorComputerName, and CreatorName as the computer I am running it on and the NT_AUTHORITY\SYSTEM account which is the same account the SQL Server Agent service is logging in with. Isn't that the whole point of the proxy account is to run the job with the appropriate permissions? It would seem as if I have the permissions with the system account.

Same with methods suggesting to change the password in the command line or creating a configuration file. Isn't the whole point of these options to override the settings in the package with proper credentials? I am not sure what I can override the system account with that will work if the package has that account as the creator.