How to identify if your car is impacted by SFD2

[tracktoy]

As I am sure you are aware VAG have introduced a new security feature on top of the existing SFD protection.

This variant begins with some vehicles from model year and will also affect new models from model year 2024.

If you would like to read the detailed information about UNECE R155 & R156, you can do so on the UN website.

UN Regulation No. 155 - Cyber security

UN Regulation No. 156 - Software update

Vehicle list SFD2 (as of February 22, 2024)

The following vehicles are currently known to be protected by SFD2:

VW Touareg (CR) facelift from model year 2024
VW Passat B9 (CJ) from model year
VW Tiguan (CT) from model year 2024
VW ID.7 (ED) from model year 2024
Audi Q8 e-tron (GE) from model year 2024
Audi A6 Avant (F2) from model year 2024
Audi e-tron GT (FW) from 2024

But this list will expand.

The .rod file on VCDS is the same as the ODX File name that you can find in Info on the OBD11 App.

Please remember not all control units will be impacted by this change but if your ODX File name

Confirmation of the above from OBD11 Support

Renatas from OBDeleven​

14:27 (2 hours ago)

Hello, Thank you for getting back to me. I was informed that the SFD2 protected vehicles control unit ODX name has the ending of "UNECE". You can check that by going to your vehicle's Gateway 19 control unit > About > check the ODX name if it has the keyword.

 

[tracktoy]

And just to update this thread I have seen this post today on the OBD11 Forum

Thanks to BRKICA

After discussions with retrofitters and VW engineers, here is what I know about SFD2:

- SFD2 was implemented as a result of passing stricter EU legislations for vehicles. The legislations in question are: UNECE R155 (Cyber Security and Cyber Security Management System [CSMS]) & UNECE R156 (Software Update and Software Update Management Systems [SUMS])

- SFD2 does not work like SFD. A SFD2 token is a two part authentication token - release is granted if a part of the token stored on your cars unit matches with the half stored on VW servers. It is possible that a 3rd party will never be able to unlock an SFD2 protected unit as they would require unprecedented access to VW databases... I don't know if VW will go for that. But, VW likes money, so given time we might get SFD2 capable 3rd party diagnostics, but for sure it won't be cheap...

- Even for online ODIS, some changes cannot be done - my colleague with dealership access rights to ODIS had issue disabling ISA (Intelligent speed assist) on a Golf 8 FL. I assume it will be the same for disabling other "safety features" due to stricter regulatory pressures on VW from the legislative body of the EU to have them active.

- Even with ODIS you need to pay a "session fee" to log into a SFD2 protected unit. It is a true money drain. One coding session (per unit) is cca 130 euro + VAT. Now imagine coding a feature spread across several units...
- Adding or swapping SFD2 protected units might not be possible - for an unit not originally fitted to the car, the SFD2 tokens on the unit and VW server won't match, possibly blocking parametrization of the unit.

So guys, if you like to work on your car it's is best to stick to the pre-SFD2 models. Might take a while before we can do anything to the new cars.

 

[cairus]

There are already several third-party providers that can open SFD 2, for example Bosch Esitronic with KTS 560.

 

[tracktoy]

I would agree there are some tools that can do it but we are talking thousands of euro's to buy and yearly license so not the sort of tool most people on this site would use.

I am also unclear i the tools work on there own or you need a Geko account or some other access to VAG Servers.

 

[cairus]

Yes, you need a Bosch-Single-Key-ID to login and authenticate you on VAG Servers.