github PaladinCloud/CE 1.3.0
on GitHub

latest releases: 3.0.6, 3.0.5, 3.0.4...
2 years ago

Policy/Rule Updates

  • Added new policies across the three clouds AWS, Azure and GCP
  • Fixed the bugs with the existing policy metadata/documentation.
  • We are improving the WiKI with the existing rules. This is an ongoing effort.
  • Added an Autofix for AWS to support unused security groups. Please refer to this wiki for details of enabling the same.

Using Azure AD

  • Azure AD can now be used as an authentication mechanism over the default db-based authentication.
  • We have tested this feature and it is fully functional. Please read the docs here to start using it.

UI Updates

  • Fixed minor bugs across the application.

Infrastructure Updates

  • Upgraded the instance types for our RDS and Elasticsearch services. This has been updated in the installer/settings/default.local.py file.
  • If you are upgrading from earlier versions, please copy your existing local.py changes to the new default.local.py and create a new local.py file. This way all the latest changes from default.local.py would be copied over to local.py. This is required as your current local.py file was created based on the previous version of default.local.py
  • Please log an issue in case of any other clarification is needed.
  • Please read the WiKi for upgrade here.

Other Updates

  • We have changed the way of adding new AWS client accounts into Paladin Cloud.
  • Earlier the addition of AWS accounts to scan is a manual process and would need to redo the process for every upgrade.
  • Now we have added the support of adding the accounts through the installer/redeploy process.
  • Users need to provide the account id and names during the installation/redeploy process as below: 
AWS_ACCOUNT_DETAILS = [
   {
       'accountId': "176332",
       'accountName': "baseAccount"
   },
   {
       'accountId': "2345",
       'accountName': "clientAccount1"
   },
   {
       'accountId': "234565",
       'accountName': "clientAccount2"
   }
]
  • As a one-time process, existing users need to add their base account information (where Paladin Cloud is installed) along with their other accounts which Paladin already monitoring, in the local.py file as mentioned above before their redeploy process.
  • Docs for adding the new AWS account to monitor are here.

Known Issues

  • Below 3 new policies are still under development and have not been fully functional yet. We will be fixing them in the upcoming release.
    • Enable hardware MFA for the root account (AWS)
    • Enable Client certificates on WebApp (Azure)
    • Enable minimum TLS version 1.2 on WebApp (Azure)

What's Changed

Full Changelog: 1.2.0...1.3.0

Check out latest releases or
releases around PaladinCloud/CE 1.3.0

Don't miss a new CE release

NewReleases is sending notifications on new releases.

Get notifications