Jump to content

Recommended Posts

  • Administrators
Posted

Hi @Mr. C,

We use static code analysis to ensure that our code doesn't contain any vulnerabilities along with industry standard procedures for reviewing and testing code and binaries before any release.

-Paul

Posted
4 minutes ago, Paul said:

We use static code analysis to ensure that our code doesn't contain any vulnerabilities along with industry standard procedures for reviewing and testing code and binaries before any release

Thanks for the info, but I would assume that this is industry standard and that Kaseya used a similar procedure, so in the current situation this is not the relief we are watintg for

Posted
6 hours ago, Paul said:

Hi @Mr. C,

We use static code analysis to ensure that our code doesn't contain any vulnerabilities along with industry standard procedures for reviewing and testing code and binaries before any release.

-Paul

That is not very reassuring. Pulseway is obviously a target here and really needs to retain a respectable cybersecurity firm to conduct a series of third party audits on the code, the dependencies of the code, and the processes used for building and deploying that code. 

 

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...