最近の検索
最近の検索はありません

Vinicius Henrique da Silva
参加日2022年11月25日
·
前回のアクティビティ2025年2月20日
Monitor de Costumer Service na Panasonic do Brasil
フォロー中
0
フォロワー
2
合計アクティビティ
259
投票
44
受信登録
84
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Vinicius Henrique da Silva
Vinicius Henrique da Silvaさんがコメントを作成しました:
Olá Anton de Young ? alguma resposta
コメントを表示 · 投稿日時:2025年2月20日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
Ao migrar para as mensagens, como obtenho esse mesmo relátório?
コメントを表示 · 投稿日時:2025年2月19日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
até quando o web widget vai funcionar?
コメントを表示 · 投稿日時:2025年1月03日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんが投稿を作成しました:
Dear Zendesk Team,
I would like to raise a concern regarding the authentication feature in Zendesk that allows users to select "Don't ask again for this computer for 30 days."
While I understand that this functionality is designed to improve user convenience, it introduces significant security risks, particularly in corporate environments where security must be a top priority.
-
Reduced Effectiveness of Two-Factor Authentication (2FA):
This option bypasses the second factor of authentication for an extended period, effectively downgrading 2FA to password-only authentication during that time. This significantly undermines the security purpose of 2FA, which is intended to protect against risks such as phishing or credential theft. -
Risk from Compromised Devices:
If a device is shared, stolen, or accessed improperly, attackers can easily bypass the additional protection offered by 2FA. The locally stored token or cookie used to "remember" the device can be exploited if compromised, potentially exposing associated accounts. -
Impact on Compliance and Security Policies:
Organizations adhering to strict data protection regulations or security policies may find it challenging to justify the use of this feature, as it undermines the principles of multi-factor authentication.
Recommendations:
- Enable administrators to disable this option at the account level, enhancing security for organizations with stringent policies.
- Reduce the "remember me" period to a more secure timeframe, such as 7 days, or implement periodic reconfirmation of credentials.
- Provide logging or alerts in the Security Center when users utilize this option, offering greater control and visibility for administrators.
Thank you for your attention to this matter. I would appreciate understanding what measures might be implemented to enhance the security of this feature.
Best regards,
投稿日時:2024年12月27日 · Vinicius Henrique da Silva
1
フォロワー
4
投票
2
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
Dear Zendesk Team,
I would like to raise a concern regarding the authentication feature in Zendesk that allows users to select "Don't ask again for this computer for 30 days."
While I understand that this functionality is designed to improve user convenience, it introduces significant security risks, particularly in corporate environments where security must be a top priority.
-
Reduced Effectiveness of Two-Factor Authentication (2FA):
This option bypasses the second factor of authentication for an extended period, effectively downgrading 2FA to password-only authentication during that time. This significantly undermines the security purpose of 2FA, which is intended to protect against risks such as phishing or credential theft. -
Risk from Compromised Devices:
If a device is shared, stolen, or accessed improperly, attackers can easily bypass the additional protection offered by 2FA. The locally stored token or cookie used to "remember" the device can be exploited if compromised, potentially exposing associated accounts. -
Impact on Compliance and Security Policies:
Organizations adhering to strict data protection regulations or security policies may find it challenging to justify the use of this feature, as it undermines the principles of multi-factor authentication.
Recommendations:
- Enable administrators to disable this option at the account level, enhancing security for organizations with stringent policies.
- Reduce the "remember me" period to a more secure timeframe, such as 7 days, or implement periodic reconfirmation of credentials.
- Provide logging or alerts in the Security Center when users utilize this option, offering greater control and visibility for administrators.
Thank you for your attention to this matter. I would appreciate understanding what measures might be implemented to enhance the security of this feature.
Best regards,
コメントを表示 · 投稿日時:2024年12月27日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
A ideia é boa, mas 1 condição apenas?
como garantir que outros tipos de tickets não sejam excluídos, nao faz sentido.
Exemplo:
Tenho 1 grupo no qual quero excluir tickets dele, entretanto não quero que contenha alguma tag especifica.
Mas somente desse grupo em específico, outros grupos talvez não fosse necessário. Não há como fazer isso.
Meio sem nexo essa opção para uma manutenção correta de tickets e dados.
コメントを表示 · 投稿日時:2024年12月12日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
Um absurdo isso não estar disponível para todas as contas ou ao menos ter a opção de Add On.
Algo que deveria ser nativo da plataforma.
コメントを表示 · 投稿日時:2024年12月10日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
Does this mean that now it is possible to use the ticket file with agent light? in order to maintain communication between departments only?
コメントを表示 · 投稿日時:2024年12月03日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
This ongoing issue with WhatsApp tickets appearing in the chat panel is completely unacceptable. We first reported this back in July, and to date, no solution has been provided.
This is not just a technical inconvenience; it directly impacts customer experience (CX) and our customer service (CS) operations. Misalignment in tools disrupts workflows, creates confusion for agents, and risks delays in response times. These are outcomes that no company aiming for excellent CX can tolerate.
The fact that not all customers are reporting this issue does not diminish its importance. A problem of this nature affects trust in your platform, and as a customer, I find it unacceptable that such a critical flaw has been deprioritized for months.
Zendesk positions itself as a leader in the CX space, yet this prolonged delay in addressing a core functionality issue raises serious questions about your commitment to your customers. How are we supposed to ensure a seamless experience for our customers if the tools we rely on are unreliable?
We demand an immediate escalation of this ticket, with a clear action plan and timeline for resolution. Anything less is a failure of the standards Zendesk claims to uphold.
I expect a detailed response promptly.

コメントを表示 · 投稿日時:2024年11月21日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント
Vinicius Henrique da Silvaさんがコメントを作成しました:
menos de 50 dias para 2025 e o Zendesk não criou NADA que pudesse resolver isso.
A recomendação da plataforma é vc criar vários usuários dentro da conta pra fazer isso.
Decepcionante.
コメントを表示 · 投稿日時:2024年11月12日 · Vinicius Henrique da Silva
0
フォロワー
0
投票
0
コメント