Best Practice For REDO Logs when storage is a storage network

I am reviewing the redo log configuration for the company. Their storage is presented from a storage device that has disk redundancy built in for maximum security against disk failure.

The redo logs are configured with only 1 member in each group. Typically I would have at least two members in each group with each member on a separate disk. In this case, I could request a new disk be added to the server and add an additional member to each group but it will still come from the same storage pool that the current disk for the redo logs.

What is the best practice for redo logs when the storage is not physical disks but a storage network system? Is it still best practice to have multiple members? It seems like the only thing that would protect you against is someone deleting the redo logs.