WhiteSource Diffend detects and blocks malicious dependency updates.
Diffend acts as a shield between you and the wild world of open-source libraries, allowing you to define policies around the usage of libraries and their versions.
Under the hood, we run extensive security checks to find potential vulnerabilities and exploits.
When you run your package manager commands with our plugin, all of this knowledge, policies and research is combined into one easy-to-understand verdict that you or your security team can use to control and mitigate potential problems before they hit production.
The Diffend heuristics learn with each package release and whenever we discover anything that would pose a threat to your organization, we will notify you about it.
Configuring a New Prospect
Prerequisites: Register the account.
We understand, that not everyone feels comfortable executing remote scripts. That is why there are two ways of setting up WhiteSource Diffend and you can choose which one suits you better.
The end result is exactly the same, since the script just automates the files configuration.
The .diffend.ymlfile can be safely committed and shared in both closed-source and open-source projects.
With our UI
Navigate to your organization projects list.
Click the Setup button.
In the setup view, navigate to the By applying changes manually section.
To set up WhiteSource Diffend, create a .diffend.yml file in the main directory of the project and copy-paste the configuration settings from the UI.
Follow the remaining instructions specific to the package manager you are using.
Add our bundler plugin and our gem right after the source section of your Gemfile.
bundle install and you are ready to go!
Yarn 2 setup
Add our Yarn plugin to the .yarn directory of your project by running the following code:
Add the following lines to your .yarnrc file:
Run yarn install and you are ready to go!
Setting up an account using the UI does not require a big effort.
With our setup script (Ruby only)
This script will add a .diffend.yml configuration file and will add our plugin to your Gemfile.
Navigate to your organization projects list.
Click the Setup button.
In the setup view, navigate to the With our setup script (Ruby only) section.
Copy the displayed command into your shell and press Enter.
Once you've executed the script, you will end up with a URL pointing to your first security verdict.
None of the changes we make will be committed, so you can review them before you add anything to your project.
Feel free to open the script URL and review all of its content before deciding on running it.
The easiest way to set up your project is to run the install script and follow the instructions.
Running Diffend Checks
WhiteSource Diffend plugin runs automatically when the following commands are executed:
bundle exec (for environments other than test and development)
bundle secure (introduced by the Ruby plugin)
Whenever you run any of those commands, WhiteSource Diffend will make sure that the packages you are trying to download or use are safe and that they meet all the requirements of the organization. This process is fully automatic and you do not have to do anything.
The secure command can be used as a separate step in a CI/CD pipeline to ensure everything is as expected.
In case WhiteSource Diffend would stop the bundle process, it will exit with an exit code 1 and will print out the security verdict URL that you can visit for more details.
WhiteSource Diffend won't stop the execution of any exec commands. Instead if needed, it will issue a warning verdict on the UI.
WhiteSource Diffend works automatically each time you run bundle commands.
Reviewing and Understanding the Security Verdicts
Security verdicts are an essential part of WhiteSource Diffend. They ensure that all of your organization requirements in the context of each bundle operation are met. That way we can prevent the usage of packages and their versions that could cause engineering and legal harm.
Each aspect that we check has a dedicated component called guard. Guards can be configured as well as disabled in the Security guards settings section of your organization if they don't meet your requirements.
After running, Diffend can give you one of the following verdicts:
allow - everything is good.
warn - something was off but we did not stop the execution.
deny - command execution has been stopped.
All of them correspond with the verdicts you can see on the UI.
Any non-allow verdict means, that something is not meeting with your organization’s security and quality requirements.
When you open the verdict page, you will be presented with all the guards that had doubts in regards to your packages.
You can disable particular guards actions for both packages and their versions in the Gems and versions usage section of your organization settings or by clicking on the gem name or its version on the verdict view directly.
Note: Direct packages and versions usage override on the verdict page do not work for all the guards yet.
WhiteSource Diffend is configurable because a single optimal set of settings does not exist. A lot depends on the type of organization you are in, projects you build, and customers you have.
If you have any doubts or need any help figuring out a proper setup for yourself, don't hesitate to contact us.
You should review any non-allow verdicts that we tell you about.
Setting up maximum verdict for particular commands
When using WhiteSource Diffend in a legacy system, you may notice, that getting things to a stable and secure state may take a while.
To prevent WhiteSource Diffend from blocking all of the commands, you may lower the maximum verdict it reports.
Navigate to the Plugin behaviour settings page of the appropriate technology of your organization.
Select the maximum verdict for a given command.
Press the Save button.
That way you can slowly resolve all of the reported issues one after another, without blocking the development of your project.
You can use our Quality Score to keep track of the improvement of your dependencies setup.
Understanding Quality Score
Quality Score is a numeric value in between 0 and 100 that is supposed to give you a quick overview of the state of your Gemfile.
It is built based on the sub-scores from each of the Guards. By looking at it, you can see the trend in which your project is going and you can make decisions whenever you see quality degradation.
You can use our Quality Score to keep track of the improvements of your Gemfile.
Re-running checks from the UI
When you apply changes to your configuration, you may want to check how it affects the bundling process you were running. You can either run the given command you were interested in again to see a new verdict or you can re-run the checks directly from the UI, by clicking on the Re-run checks button.
The Re-run checks button is available for the security verdicts except those that were finished without any issues. It is available above the successful verdicts on the right side of the UI.
Re-running checks is the easiest way to see how your changes will affect execution of the given command.
Continuous Integration and Delivery environment setup
WhiteSource Diffend protects every crucial bundle command out of the box, but you can still easily set it up as a separate step within your Continuous Integration and Delivery system.
Doing so will allow you to receive notifications based on the CI/CD results via our notifications system.
To set it up, please follow the instructions for the appropriate CI/CD system.
If you are using a different CI system, the setup should be similar. Please contact us if you have examples of other CI systems.
Deployment and production environment setup
WhiteSource Diffend requires minimal effort to make it work with the majority of ways you can deploy your applications. If there are no hints below for your way of deployment, it means, that all you need to do is:
Setup the DIFFEND_ENV variable to match your deployment environment.
Make sure, that you have the .diffend.yml in your version control system.
You need to remember about setting the DIFFEND_ENV to match your environment.
Please make sure, to always run bundle install instead of running bundle check. To do so, put the following code in your deploy.rb file:
Make sure, that the .bundle directory is not amongst the linked_dirs.
The changes you need to make, come from limitations of the Bundler plugin system.
Please make sure, that the .diffend.yml file is included before you run any bundle commands during the container build process.
To do so, add the .diffend.yml file into your Dockerfile, before adding the Gemfile and Gemfile.lock:
.diffend.yml file needs to be present before running any bundle commands.
When using Heroku, please make sure, that the .diffend.yml file is included before you run any bundle commands during the container build process.
If you are using the Heroku Buildpack for Ruby applications you need to set up following environment variables based on the .diffend.yml file content:
Heroku Buildpack for Ruby requires you to set the three environment variables mentioned above.
Diffend monitor gem keeps track of the state of your deployment environments automatically.
Thanks to that, whenever a new threat that could pose a risk to your application is being detected, we can notify you about that using Slack.
In order to receive bundle exec related notifications from environments like staging or production, diffend-monitor needs to be present in your Gemfile.
Notifications are a great way to make sure, that your team becomes aware of emerging vulnerabilities the moment they are detected.
Connecting WhiteSource Diffend to Slack
Navigate to the Notifications settings page of your organization.
Press the here link visible in the information box. You will be redirected to the Slack platform settings page.
Select a channel where you want WhiteSource Diffend to post security notifications and press the Allow button.
You will be redirected back to the WhiteSource Diffend notification settings page and a Slack welcome message will be sent to your workspace channel.
WhiteSource Diffend sends messages based on events that occur while protecting your applications. Below you can find a list of the events that trigger notifications, together with their short descriptions and other useful details.
New bundle state detected
Other than development and test
WhiteSource Diffend emits message based on this event whenever you deploy changed to your Gemfile that affect given environment.
Awareness of newly updated libraries deployed can help you debug when your new code presents unexpected behaviors.
New verdict detected
Other than development and test
WhiteSource Diffend emits a message based on this event whenever the verdict associated with your deployment has changed.
Bundle secure execution alert
WhiteSource Diffend emits a message based on this event whenever there is anything in your Gemfile that requires attention.
While we are sorry to see you go, we won't make things hard for you. We just kindly ask you to provide us with any feedback you might have on the reasons.
Removing Bundler plugin and gem
Due to some Bundler limitations, you will have to re-bundle your project after removing appropriate files. Just run the code below inside of your project main directory.
Removing Yarn 2 plugin
Due to some Yarn 2 limitations, you will have to re-run the install command after removing appropriate files. Just run the code below inside of your project main directory.
Questions and answers
Can the .diffend.yml file be committed into our repository version control system?
Yes. This file contains only shareable keys with write-only permissions. The only thing you need to keep in mind in case of open-source projects, is that you will see results of all the security checks of whoever runs your project.
Why bundle exec won't stop despite a warning verdict?
By default, we don't want to stop your running processes or cause any unpredictability in the code execution. Please contact us, if this is a functionality you would want to see.
We are working on a notifications engine that will notify you the moment any threat is detected that could cause risks to your production running processes.
Do you send private packages credentials to your servers?
No. All the private repository credentials and other private data is being stripped away before anything is being sent to us.
Just in case, we also have an extra sanitization layer in the API. Even if any private details would be sent, they do not end up being stored or used.
Is it safe to have diffend-monitor running in production environment?
Yes. diffend-monitor never executes any code in response to our platform replies. It does not rely on the response content for operations. Its primary purpose is to ping our servers periodically, so we know that the given process is running. We need this information for our real-time monitoring services.
Bundler plugin is not working as expected. What should I do?
First of all, try to reinstall the plugin by running the following commands in your project root directory:
Does WhiteSource Diffend take into consideration Bundler groups?
Both plugin and the monitor operate in the current Bundler execution context.
That means that we won't notify you about issues with gems in your Gemfile that do not pose any risk as they are not being downloaded or executed.
That is why it is essential to use both the plugin and the monitor to integrate WhiteSource Diffend within your CI system.