What is our primary use case?
Customers use DigiCert Secure App Service primarily for code signing. This involves signing code from the developer for applications on Android or iOS before uploading to the Play Store or App Store.
The aim is to ensure secure and verified code signing, especially for mobile applications. For instance, when an application is developed using Microsoft technologies, it's crucial to have a secure signing process to prevent Microsoft Defender from flagging the code as malicious. This security measure is achieved through digital signing certificates.
Additionally, DigiCert Secure App Service is used for signing various files, like BrasCo files and Excel files, which are then distributed to various brands, including banks and telecommunication companies.
This service ensures that these applications are safely installed on Microsoft Windows without being flagged by Defender, as they are verified and signed.
The co-signing certificate is specifically for signing code during development before uploading to a customer.
How has it helped my organization?
With the DigiCert Secure App Service, if you need to order code signing for multiple applications, it's no problem; you can do it with just one order. This is similar to SSL certificates, where you can have one SSL or one common name.
For code signing, one certificate is sufficient for signing many applications, whether it's APK for Android or IPF for iOS. And for Windows applications that connect to the Internet, one certificate works well. The code signing aspect is okay.
The current functionality, like signing APKs or IPAs for iOS to be uploaded to the Play Store or App Store, is sufficient for our needs in terms of code signing.
What is most valuable?
One of the most valuable features is its ability to detect and prevent malware. Every operating system has a built-in firewall, like Microsoft's Windows Defender. However, if you install additional software from an in-house developer, Windows Defender may flag it as malware.
This can even happen with in-house software developed by banks or telecommunications companies. So, how do you solve this problem? After all, you've invested time and effort into developing this code. The solution is to use the code signing feature of SecureApp. Once you sign your code with a trusted certificate, Windows Defender will recognize it as legitimate and allow it to run.
After that, you can deploy your software using patch management tools like Ivanti or SCCM, or you can install it directly on the network.
For the actual signing bit, it's straightforward enough – like, we got an APK or an IPA for an iOS phone, and we want to shoot it over to the Play Store or App Store. It’s all about that code-signing function.
We have one certificate for signing the production code and another certificate for signing the test code. A function for a co-signing certificate. However, it is not available for the cloud.
What needs improvement?
DigiCert has a secret server management feature in the deviated version, particularly for PKI integration. They could enhance the integration with monitoring tools. It would be beneficial to monitor how many extras are installed at each branch. The most significant improvement would be a monitoring tool for the signing code.
For how long have I used the solution?
I have been using this solution for two years now.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It is a scalable solution. However, people do not have a lot of experience with digital certificates in Jakarta or Indonesia.
So, the scalability is limited to 1,000 users for the local server certificate and one code signing certificate.
My company has two end users using this solution.
How are customer service and support?
There is 24/7 support available.
But if there's a need to go through a solution, even for a banking article related to a signing solution, that's me. I handle those, not through the user's portal, but I assist with finishing it personally.
Which solution did I use previously and why did I switch?
I tried Microsoft, which integrates well with Java.
How was the initial setup?
I find it very easy. The process includes requesting and validating. For code signing, you need a USB token. If you don't have one, DigiCert can provide a token for around a hundred bucks.
The token is sent by mail, and my customer receives it. Once you have the USB token, you can configure it to your laptop the next day, prepare your coding, and once you're ready to upload your app or extra file to the app store, you can easily sign the code with the DigiCert code signing service. It's a very straightforward process. It takes around one hour to configure and sign the code.
There is no maintenance required. You just need to renew your license.
What's my experience with pricing, setup cost, and licensing?
What other advice do I have?
Overall, I would rate the solution a ten out of ten because it's user-friendly, very easy to use, and provides 24-hour support.
Which deployment model are you using for this solution?
Public Cloud