CoSign Cloud - Possible to sign binary file or buffer? (Detached Signature) - digital-signature

The CoSign documentation indicates that is possible to sign an arbitrary binary buffer and create a detached signature. See http://developer.arx.com/examples/sapi_local_detached_signatures/
However, looking at the WebAgent and SOAP API docs this does not seem to be correct.
Question: Is this only supported for the local API?

In addition to Larry's answer, note that you can easily sign buffers using the CoSign Signature API.
Also, here you can the API endpoint for CoSign Cloud.

The web agent api signs pdf, word, and excel docs.
The CoSign Signature, Local, and Soap APIs can be used to sign data buffers. They can be used with the CoSign cloud service or with a CoSign appliance.
Please note that the cloud service may not be used for batch signing.

Related

Docusign Document Encrypt and decrypt using query parameters encrypt set to true in Docusign

In docusign while downloading documents using getDocuments API and when we want to set encrypt to true, it says NO_SECUITY_APPLIANCE_CONFIGURED for this account. How to configure/enable security appliance for docusign's account?
NOTE: Though all docusign's API's are TLS/SSL enabled, I still want to encrypt and decrypt documents
In order to enable the GetDocuments Encryption parameters, you'll need a DocuSign Security Appliance: An on-prem device that holds your encryption keys within your network.
More information on that is available here: https://www.docusign.com/products/hybrid-cloud-appliances
Contact Sales if you're interested in moving forward in that direction.

How to save SubscriptionKey on javascript

I make speech recognition App using Bing speech API with javascript library.
But I need to contain SubscriptionKey to Html/JS code using Library.
I think another person can see my key and use it.
How to save my key?
Can regenerate key dynamically on each user access?
or
Can set expire limitation to key?
You are recommended to make calls from the server side. You can initiate a call from your client to server, where your client is whitelisted and then make a call to the API. Alternately, you can use Azure Key Vault to generate secret and use that and change that often. Further, you are recommended to change subscription keys and/or Azure Key Vault secret often to limit exposure.
A similar question but for Bing Maps is posted here: http://www.garzilla.net/vemaps/Protecting-Your-Map-Key.aspx.

Can webhooks be delivered straight to Azure Event Hubs?

I've read a lot of documentation on Azure about working with Shared Access Signatures, and I don't believe it's possible to have webhooks delivered straight to Evenhtubs. I believe an intermediate service like a an Azure Function or Logic App currently needs to act as a middleman.
Is it correct to say that the service generating the webhook would have to choose to implement the signing scheme used by Azure Shared Access Signatures for Eventhubs to receive such a webhook?
Furthermore, is there any Azure PAAS service such as document DB or Azure SQL which has an API authentication scheme which a fairly simple webhook could write directly to?
It's been awhile since this question was asked but I'll put the answer here for anyone who needs it.
Yes, you can have a webhook send directly to an Event Hub. The client needs to send a post request with the Shared Access Signature (SAS) in the Authorization header and data in the body.
Here is Microsoft's documentation on the process.
https://learn.microsoft.com/en-us/rest/api/eventhub/send-event

3rd Party Key Storage Providers

Can we persist keys in 3rd party key stores? We do not want to store in Microsoft Keys Store. Any clue for such providers and samples/documentation will be helpful.
If I understand you right, Key Vault in Microsoft Azure is what you are looking for.
The problem, however, is that at the moment this API is not easily useable in a transparent manner, i.e. you need to explicitly call API functions via the provided Vault SDK.

How can an application store secrets in Google Cloud Datastore securely?

I am building an application that will run on Google App Engine (GAE). It will need access to data stored by the user in other systems (e.g. the user's Nest thermostat, Yahoo mail). The application running on GAE will allow the user to provide credentials for the other system. The application will store these credentials in Google Cloud (Datastore) for later use by an application running on Google Compute Engine on the users behalf. The application will also allow OAuth to allow the user to allow the application access the external system in the user's behalf. The application will need to store user credentials (username and passwords) or OAuth access tokens in the Google Cloud.
The application will need to encrypt the secrets before they are stored and be able to unencrypt the data to send it to the external systems. That is, the system will need to use symmetric encryption and therefor need to securely manage keys.
How can the application store these secrets in the Google Cloud Datastore (Datastore) securely? I think I am looking for something like the AWS CloudHSM for Google. That is, I would like to store each secret with a seed and key id and use the key id to get the key from a key management system. This implementation would also allow for key rotation and other standard security practices.
I think I am looking for a Google Cloud service or Google API that provides secrets management and only allows an app with the proper Google app identifier to access the secrets.
Is there a service within Google Cloud or Google APIs that will manage secrets? Is there another architecture that I should be considering?
By the way, the application uses Google Identity Toolkit (GitKit) to authenticate and authorize users to use the GAE hosted application. The application allows users to create accounts using either federate identities or username and passwords via GitKit.
Thanks,
chris
In the meantime, Google also added a Key Management Service: https://cloud.google.com/kms/
You could e.g. use it to encrypt your data before storing it in a database. Or, use KMS to encrypt an AES key to encrypt your data, and possibly keep a backup of your AES key somewhere in case you lose access to KMS.
App Identity Service might be what you are looking for https://cloud.google.com/appengine/docs/java/appidentity/#Java_Asserting_identity_to_other_systems
It lets you sign content with an application-specific private key, and provides rotating certificates to validate signed content.
So as far as I can tell the answer is that you can't. What you are looking for is an equivalent to KMS. That service let's you create and manage keys and do a bunch of your own crypto stuff. It's really cool and it will allow you to quickly do incredibly strong crypto with just a few simple lines of code. Azure has a similar service called KeyVault. It lacks automated key generation and rotation as far as I can tell, but other than that it's good. At the time of this response there was not an equivalent service for Google. They have an internal KMS which they used for crypto operations and you can provide your own keys, but that's pretty much it. Not quite the same thing that you get on KeyVault, and nothing like KMS.
That said there is hope. You can do one of two things:
Create a VPC and use an HSM from somewhere else. You could use RackSpace, or you could simply use AWS KMS. That sounds crazy but it's actually a good idea and the extra management is worth it. In general the most secure solution separate the keys from the encrypted data, particularly at rest. That means that keys in one data center and encrypted data stored in another data center is the most secure solution. That sounds like hard stuff, but thankfully I've made an opensource project which makes it very easy for you called KeyStor. With KeyStor you can get a data center that deals with encryption services set up in a day, no problem, and you can use AWS very cost effectively.
Set up your own cypto service, skip the HSM integration and simply be careful about who has access to the machines that maintain your keys. You can do this with KeyStor as well, and if KeyStor doesn't quite do what you want, that's why it's open-source. Take the code and build what you need to build.
You could store secrets in storage (e.g., in Datastore, Google Cloud Storage, or another storage system of your choice) and encrypt those with a key from Google's Cloud KMS.
Here's some documentation from Google on secret management, and here's a codelab on specifically encrypting data in Google Cloud Storage at the application layer using Cloud KMS.
For the Google Cloud managed service that provides the API for secure storage of secrets, see Google Cloud Secret Manager for more details.
Secret Manager is a secure and convenient storage system for API keys, passwords, certificates, and other sensitive data. Secret Manager provides a central place and single source of truth to manage, access, and audit secrets across Google Cloud.

Resources