My main use case for AppViewX CERT+ includes three business cases that I can explain. For internal websites that we have in the company, we share with the business and provide because we need to be completely secure with this environment. Each business owner and developers request internal certificates. We now have a workflow that they can request from our management tool. They request the certificate and then the certificate team, with AppViewX CERT+, generates the certificate for them and pushes them directly to the server where it's deployed without requiring anything on their side. The second case is for public certificates, all the websites and SaaS environment that we use, which we provide to the business and external clients. This workflow differs because it involves public certificates approved by our public authority. This process is closely tied to the business as they need to ensure certificate validity, especially when planning to move URLs or stop services within six to eight months, due to associated costs. The process is similar to internal websites but requires change management for production. The process varies depending on whether the SaaS application is in our cloud environment or managed by a provider. In both cases, we create the certificate with AppViewX CERT+, generate it, verify DNS entries for public authority validation, and then either push it ourselves if we manage the backend or coordinate with the provider to implement it. The third business case involves application and mobile application coding. We have specific workflows and certificate possibilities that are highly integrated with the automation process, especially for APIs. Our developers create numerous APIs for clients, ranging from two or three per month to sometimes more than 100. We have created an automation process that generates certificates for varying periods depending on API requirements.
My main use case for AppViewX CERT+ includes three business cases that I can explain. For internal websites that we have in the company, we share with the business and provide because we need to be completely secure with this environment. Each business owner and developers request internal certificates. We now have a workflow that they can request from our management tool. They request the certificate and then the certificate team, with AppViewX CERT+, generates the certificate for them and pushes them directly to the server where it's deployed without requiring anything on their side. The second case is for public certificates, all the websites and SaaS environment that we use, which we provide to the business and external clients. This workflow differs because it involves public certificates approved by our public authority. This process is closely tied to the business as they need to ensure certificate validity, especially when planning to move URLs or stop services within six to eight months, due to associated costs. The process is similar to internal websites but requires change management for production. The process varies depending on whether the SaaS application is in our cloud environment or managed by a provider. In both cases, we create the certificate with AppViewX CERT+, generate it, verify DNS entries for public authority validation, and then either push it ourselves if we manage the backend or coordinate with the provider to implement it. The third business case involves application and mobile application coding. We have specific workflows and certificate possibilities that are highly integrated with the automation process, especially for APIs. Our developers create numerous APIs for clients, ranging from two or three per month to sometimes more than 100. We have created an automation process that generates certificates for varying periods depending on API requirements.