Skip to main content
Johannes Jauch

Johannes Jauch

Axinom DRM Product Owner, CTO
View all authors

DRM Security Best Practices

· One min read
Johannes Jauch
Johannes Jauch
Axinom DRM Product Owner, CTO

Video and streaming businesses turn to Digital Rights Management (DRM) to secure their content, but simply adding DRM is not enough. The effectiveness of DRM depends on how it is implemented and how well it is integrated into a broader security strategy. Poor implementation can lead to vulnerabilities that pirates exploit, negating DRM’s intended purpose.

Our new article DRM Security Best Practices highlights best practices to maximize DRM security and avoid common pitfalls.

DRM PlayReady API 6.21.0

· One min read
Johannes Jauch
Johannes Jauch
Axinom DRM Product Owner, CTO

New release 6.21.0 of Axinom DRM License Service (PlayReady) is available!

Changes:

  • PlayReady Server SDK upgraded from v4.6.7604.13892 to v4.6.7607.0_QFE1. This is a security update released by Microsoft on Oct 26, 2024.

This is a so called required update that every licensee of the Microsoft PlayReady Server SDK has to incorporate into their Server Applications and Services within six months.

Widevine revoked CDMs

· One min read
Johannes Jauch
Johannes Jauch
Axinom DRM Product Owner, CTO

Since Google revoked CDMs for older browsers on October 31, 2024, we observe an elevated level of Widevine DRM license rejected errors. We recommend our customers to observe the client error messages, and if "revoked" errors are encountered, to update users' browsers. With the latest revocation, it requires a Chrome version 117+ to deliver a Widevine license successfully.

Encoding audio

· One min read
Johannes Jauch
Johannes Jauch
Axinom DRM Product Owner, CTO

Did you know that with Axinom DRM you can also protect pure audio files?

People usually think, DRM (like Widevine/PlayReady/FairPlay) is about video protection. It is correct, but it is NOT ONLY about video. If you have an audio file (say, MP3), you can feed it to Axinom Encoding, which will convert it to MPEG DASH format and encrypt the audio track according to DRM standards. If you provide no video input, there will be no video track in the output DASH manifest.

You can now use all regular video players to play this asset. In UI it makes sense not to display the video area, as there is no video. But the audio track will play. All the same approaches for an entitlement message ("token") acquisition and sending it to a DRM License Service apply.

Try it out yourself.