"One last thing to keep in mind: You will not actually get SL3000 security unless the actual AES content keys used to encrypt the content are different between streams (not just the KID). It's technically possible for a license server to issue licenses with different KIDs with the same content key "
So, always need to use different distinct KID and encryption key for video track and audio tracks, if encryption key is identical then implementations will drop to SL2000 and not use SL3000.
PlayReady SL3000 issues discussed in DASH-IF noted by @Murmur for HbbTV service implementers to be aware of:
https://github.com/Dash-Industry-Forum/dash.js/discussions/3869#discussioncomment-3528752 Note the comment from Microsoft:
So, always need to use different distinct KID and encryption key for video track and audio tracks, if encryption key is identical then implementations will drop to SL2000 and not use SL3000.