Skip to content

Releases: PaladinCloud/CE

1.5.1

01 Dec 18:06
@santhosh-challa santhosh-challa
1.5.1
5e3a114
Compare
Choose a tag to compare
1.5.1

Policy Updates

  • Added 41 new policies across the three clouds AWS, Azure, and GCP
  • Fixed the bugs with the existing policy metadata/documentation.
  • We are improving the wiki for the existing rules. This is an ongoing effort.

UI Updates

  • Fixed bugs across the application

Installer Changes:

  • We have removed the AWS ReadOnlyAccess policy from the installer role. Instead, we have added individual service-level policies to the installer. Now, users do need to add the ReadOnlyAccess policy to the paladicloud_ro role. We will be updating the installer docs regarding the policies required to install the Paladin Cloud.
  • We have fixed the issues in the Qualys connector. It is fully functional now. We will be adding the documentation on how to add the Qualys connector.
  • Now users do not need to modify the existing security grp to make the app work. We have added the required inbound rules as part of the installer itself.
  • We have corrected the minor variable names in the default.local.py file. Existing users will have to recreate the local.py in order to avoid redeploy issues.

What's Changed

Read more

Contributors

santhosh-challa, raviteja-mandala, and 10 other contributors
Assets 2

1.5.0

28 Oct 15:36
@santhosh-challa santhosh-challa
1.5.0
0dba024
Compare
Choose a tag to compare
1.5.0

Policy/Rule Updates

  • Added 21 new policies across the three clouds AWS, Azure, and GCP
  • Fixed the bugs with the existing policy metadata/documentation.
  • We are improving the wiki for the existing rules. This is an ongoing effort.

UI Updates

  • Added new Asset Distribution Screen.
  • Modified the dashboard violation tails to include more metadata.
  • Fixed other bugs across the application

Other Changes:

  • We have removed the Azure Policy Definitions and Policy Evaluations from assets. So existing users will be seeing Azure assets going down post-upgrade. We will be working on a feature to represent these in a better way in the coming releases.

Known Issues

  • We are testing 2 AWS and 1 Azure policy which we have added in this release. They may not be fully functional yet. We will update then in the upcoming release if necessary.

What's Changed

New Contributors

  • @MonikaSharmaZemoso made their first contribution in #544

Full Changelog: 1.4.0...1.5.0

Contributors

santhosh-challa, raviteja-mandala, and 11 other contributors
Assets 2

1.4.0

07 Oct 17:51
@dheerajkholia-paladin dheerajkholia-paladin
1.4.0
cbb87e4
Compare
Choose a tag to compare
1.4.0

Policy/Rule Updates

  • Added 19 new rules across the three clouds AWS, Azure and GCP
  • Fixed the bugs with the existing policy metadata/documentation.
  • We are improving the wiki for the existing rules. This is an ongoing effort.

UI Updates

  • Added new violations table in the violations screen.
  • Fixed bug in enabling/disabling rules.
  • Added the version number of the app on the UI screen.
  • Fixed other minor bugs across the application.

Infrastructure Updates

  • Added ability to add more nodes for open search cluster via the installer. Now users can add more nodes to the cluster as per their workloads.
    • Existing users must ensure to update their local.py configs from the new default.local.py file. This is needed for the redeploy to take the new configurations.
  • Added ability to configure RDS master user name and password via the installer. We have changed the default username and password. So existing users would see the RDS instance being destroyed and recreated. As it stores only configurations required for the application, the same would be re-created with the upgrade process.
  • Fixed an issue while adding HTTPS via the installer. This is raised in the community issues. Issue #479

What's Changed

Full Changelog: 1.3.0...1.4.0

Contributors

sidharthjain-zemoso, kushZemoso, and 7 other contributors
Assets 2

1.3.0

17 Sep 08:51
@santhosh-challa santhosh-challa
1.3.0
27ed0b0
Compare
Choose a tag to compare
1.3.0

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

Contributors

santhosh-challa, sidharthjain-zemoso, and 8 other contributors
Assets 2

1.2.0

05 Sep 06:46
@santhosh-challa santhosh-challa
1.2.0
1107ba1
Compare
Choose a tag to compare
1.2.0

Summary of Changes

EventBridge Limit:

  • Last release we crossed the default AWS account soft limit for the number of rules that can be created for an event bus (300). So we have requested users to upgrade their limit before redeploy or installation process.
  • The good news is that we have overcome that limitation in the current release using a new micro-service called job-scheduler. Now Paladin Cloud uses separate custom event buses for each cloud provider.

Policy/Rules Update:

  • We have added new collectors and rules across the three cloud providers, AWS, Azure and GCP
  • We have added our first auto-fixes for a couple of policies in Azure and GCP. We will be updating the steps required to enable the same in the wiki.
  • We have made some changes to Rule metadata.
  • We are updating the Wiki with the current rules we support. This is an ongoing effort.

UI updates:

  • We have redesigned the Policy Knowledge base screen.
  • We have added a new feature, a collapsible navigation bar
  • We have fixed an issue with the table to store the previous state
  • We have fixed minor fixes across the other components

Azure AD:

  • We have added a feature to enable Azure AD authentication in the Paladin Cloud.
  • Azure AD can now be used as an authentication mechanism over the default db-based authentication.
  • We are in the process of testing the Azure AD feature. Please watch this space for an update on the Azure AD

Infrastructure Updates:

  • As stated above, we are now using custom EventBridge buses.
  • We have created a new micro-service job-scheduler in our existing ECS cluster.
  • This microservice would emit the events periodically to trigger the jobs/rules.
  • We have upgraded the Terraform to the latest version, 1.2.x
  • If you are upgrading from previous versions, please follow this link to start upgrading to this release.

What's Changed

New Contributors

Full Changelog: 1.1.0...1.2.0

Contributors

santhosh-challa, sidharthjain-zemoso, and 9 other contributors
Assets 2

1.1.0

05 Aug 05:44
@santhosh-challa santhosh-challa
1.1.0
86d9faf
Compare
Choose a tag to compare
1.1.0

Summary

  • Added two policies for GCP
  • UI Angular Upgrade and bug fixes
  • Existing policy updates
  • Infra updates

Details

AWS Event Bus Limit:

  • By default, AWS has a soft limit on the number of rules that can be created against the default bus. Currently, this limit is set to 300.
  • We have crossed the limit in this release. If any of the users try to redeploy or install Paladin Cloud from this release, the installation will be failed due to the limit.
  • So we are requesting you to raise a support ticket with AWS to increase the Rule limit on the EventBridge bus from 300 to a bigger limit. (400/500 depending on your use cases)
  • We are working on avoiding this by using the custom event busses. This is under development and we are actively working on it to include in the next release.
  • New installations or redeployment of the existing applications need to follow the above process before the start of the process.

Policy Updates

  • We have added a new collector for AWS.
  • We have added two policies for GCP.
  • We also changed the cf_Policy table metadata along with the existing policy description updates.
  • As per the current process, redeploy will not update the existing data in the DB tables.
  • New data will be inserted during the redeploy process.
  • To get the existing updates, users who are using the Paladin Cloud optionally can follow the below process:
    • Connect to the MYSQL instance, which was installed as part of the installation
    • Truncate the two tables cf_Policy and cf_RuleInstance. The fresh data would be inserted into these tables during the redeploy process.
  • We are working on improving the data migration process.

UI Updates

  • We have upgraded the Angular library version from v4 to v13.x.
  • Please follow the below steps if you are planning the redeploy process:
    • Please remove the node_modules, dist folders and package-lock.json file.
    • This should not cause any loss to the user experience. Please raise an issue in case you are facing any issues.
  • We also added some bug fixes in this release.

Infra Updates

  • Upgraded the Lambda runtime from python3.6 to python3.8
  • Added the tags for the missing resources created via the installation process.

Known Issues

  • We have added two policies for the AWS autoscaling group in this release. They are not fully functional yet. We will be fixing the same in the upcoming release.

What's Changed

New Contributors

Full Changelog: 1.0.1...1.1.0

Contributors

praveeny1986, dependabot, and 11 other contributors
Assets 2

1.0.2

02 Aug 10:31
@santhosh-challa santhosh-challa
1.0.2
3b1241a
Compare
Choose a tag to compare
1.0.2

What's Changed

We have updated the Lamda runtime from python3.6 to python3.8. As python3.6 runtime is deprecated.

Full Changelog: 1.0.1...1.0.2

Assets 2

1.0.1

14 Jul 10:39
@santhosh-challa santhosh-challa
1.0.1
34bf7e9
Compare
Choose a tag to compare
1.0.1

What's Changed

We added minor fixes for policy, documentation and UI.

Full Changelog: 1.0.0...1.0.1

Assets 2

1.0.0

09 Jul 13:35
@santhosh-challa santhosh-challa
1.0.0
9535707
Compare
Choose a tag to compare
1.0.0

Hello Community,

The Paladin Cloud team is pleased to announce that Paladin Cloud 1.0.0 has just been released.

Paladin Cloud is an extensible, Security-as-Code platform to help developers and security teams significantly reduce risks in their cloud environments. The platform functions as a policy management plane across multi-cloud and enterprise systems to protect your applications and data.

For more information check the wiki.

Assets 2