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

Ryan Winkler
参加日2021年4月14日
·
前回のアクティビティ2025年2月03日
フォロー中
0
フォロワー
4
合計アクティビティ
229
投票
89
受信登録
92
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Ryan Winkler
Ryan Winklerさんがコメントを作成しました:
February Update:
Hey Everyone,
For anyone tuning in, since the launch of the UI, we've been busy optimising how best to provide this experience, as well as support more fields. Your feedback is KEY to prioritisation, so please don't hold back
Here are some of the key updates we have added since December
[Dec 14th release] Access Log UI: We launched the UI in Admin Center to rapidly expand the use of this feature. No longer will you need to use an API or third party connection for simply viewing.
Since the original release, notable Updates include:
- Sort by time (in the API as well!) -- ability to retrieve and view logs by latest first
-
Agent filter by name or email -- Simplify Actor look ups by a name or email!
Coming soon:
- Column manager -- show or hide certain fields in the UI!
- URL pathway filter -- Just like our API, filter activity down by URL pathway, instead of Actor, allowing you to check who viewed what specific ticket, attachment, etc.
-
Log Details panel -- A side panel to display further information, such as User Identity, and the groups they belong to.
-
Authorization Type and client (user_agent) fields: We’ve added authorization type and client details in the access logs. This enables you and your admins to see very explicitly if activity is coming from an API call, browser or otherwise. So far, we've seen this used to identify API activity and errors which may occur, as well as easier identification of usage of Tokens or non browser use. We're still looking to mature this offering so please let us know if you have any feedback related to this
GraphQL fields -- we will add columns to handle GraphQL fields in the UI!
We Need your Help!
We want to continue to build out an actionable and comprehensive feature, so we're looking for the following direct validation on the following:
-
How important is Description for you?
- We're planning to add Description and product area fields to each log event and are looking for any feedback or comments on how important this is to you
-
We have some mock ups that we would love to talk with you about (so please reach out to your Account manager to get in touch!)
-
WEBHOOKS/ Pushing data
- We've heard your need for a better way to get filtered data. We're considering adding webhooks to accommodate this. We're looking for any and all feedback relating to how this could help you with Audit Logs OR Access logs, so please send them in (as a comment or in a ticket!)
-
How important is Description for you?
Please let us know if you have any questions or concerns. Your feedback to us will help prioritise and is vital to building out the best solution, so please don't hesitate to reach out!
コメントを表示 · 編集日時:2025年2月03日 · Ryan Winkler
0
フォロワー
1
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Hey Tim Fischer !
Thanks for reaching out and providing context here. GDPR and regulatory needs are something we are sensitive to ourselves, so the need is not lost on us!
Deletion of old Audits is something we've done some basic discovery into but have not been prioritised anytime in the near future unfortunately.
Are you just worried about the logs which could have PII within it, or would you like the need to delete settings and configuration changes (Admin center) as well?
If we were to just target a specific category of logs, which log would we want that to be in?
Would love any additional context or feedback you can provide!
Thanks again for the details and feedback!
コメントを表示 · 投稿日時:2024年12月18日 · Ryan Winkler
0
フォロワー
1
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Hey Jill, Rudolph and Karl.
Firstly, Apologies for a lack of response, but secondly, we really appreciate the feedback.
Access logs being part of our Advanced data Privacy and protection add-on was an intentional choice due to the very large volume of logs (and data) that are produced. They are unsampled network logs of all agent activity within your account, which equates to millions of records (on average), which brings some large storage considerations.
We've attempted to price and provide the offiering competitively in line with similar offerings in the market, while coupling it with some key functionality to help build value even further, with more and more to come in the future.
However, I understand that cost being a huge blocker is frustrating. While I don't have any changes on pricing to provide, I can say that we are actively listening and here for you with any feedback or concerns.
Keep us honest and continue to provide us this crucial feedback. I can't promise that I will be able to resolve every concern, but I can promise to actively cheerlead for anything need cheering for!
コメントを表示 · 編集日時:2024年12月12日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント
Ryan Winklerさんが記事を作成しました:
発表日 | ロールアウト日 |
2024年12月12日 | 2024年12月12日 |
管理センターのアクセスログUIがリリースされました。アクセスログは、Zendeskアカウントのデータセキュリティと管理コントロールを強化するように設計されています。この機能は、「高度なデータプライバシーとデータ保護(ADPP)」アドオンで提供されます。
アクセスログ機能は、以前はAPIとしてのみ提供されていました。アクセスログUIのリリースにより、直接管理センターで、訪問したURLに基づいて、アクセスされた内容に関するインサイトを得ることができます。
このお知らせの内容は以下のとおりです。
機能の変更点
このリリース以前は、アクセスログのデータはAPIコールでしか利用できませんでした。なお、このリリースでは、管理センターでデータにアクセスできるようになりました
アクセスログUIは、今後数四半期にわたって追加機能で強化される予定です。このリリースにより、エージェントがZendeskアカウントで閲覧した内容に関するアクティビティを、管理センターから直接監視できます。APIを使用して情報を取得するための技術的な専門知識や時間は必要ありません。
Zendeskがこれらの変更を行う理由
Zendeskは、お客様がお客様のデータを管理できるように取り組んでいます。アクセスログUIの提供開始により、直接管理センターで、ご利用のアカウント内でのエージェントのデータアクセスを詳細に記録することで、カスタマーのプライバシーを強化することができます。アカウンタビリティを向上させ、どのエージェントが、いつ、どのIPアドレスから、どのデータを閲覧したかを確認できます。不適切なデータアクセスのリスクを特定して防止し、データプライバシー規制へのコンプライアンス準拠をサポートできます。
必要な作業
すでに「高度なデータプライバシーとデータ保護」アドオンがあり、アクセスログが有効になっている場合は、それ以上の操作は必要ありません。UIを利用できます。アクセスログを有効にしていない場合は、オンにして、UIに表示されるイベントのキャプチャを開始できます。
アクセスログを使用してZendeskアカウントを保護するシナリオの例などに関する詳細については、「アクセスログを使用したエージェントのアクティビティの監視」を参照してください。
「高度なデータプライバシーとデータ保護」アドオンの契約者ではなく、アクセスログUIにアクセスする場合は、「「高度なデータプライバシーとデータ保護」アドオンについて」を参照してください。
この発表に関連するフィードバックや質問がある場合は、コミュニティフォーラムにアクセスしてください。このフォーラムでは、カスタマーから寄せられた製品フィードバックを収集し管理しています。Zendesk製品に関する一般的なサポートについては、Zendeskカスタマーサポートにお問い合わせください。
編集日時:2024年12月17日 · Ryan Winkler
0
フォロワー
1
投票
0
コメント
Ryan Winklerさんが投稿を作成しました:
Access Log UI release
Calling ALL ADDP subscribers (or anyone thinking of subscribing for Access Logs)!
We've just released our UI for our Advanced Data Privacy and Protection Add-on feature, access logs (Announcement here).
What we're looking for
We are interested in hearing about your experience when using the Access Log UI. We're releasing today to get you access to your events in Admin Center, as we have heard that this has been a major frustration and blocker in regularly using Access logs.
While we plan to continue to make improvements over the next few quarters to this feature, we would love to hear from you on what is important, missing or needs improvement from a functionality or information basis.
You can also check back here to know any known limitations or planned fixes as well (this post will be monitored!)
How can you help
Upvote, comment, provide feedback as thoroughly as possible. We're looking for usecases and help find what is best to prioritise and when!
編集日時:2024年12月12日 · Ryan Winkler
3
フォロワー
5
投票
1
コメント
Ryan Winklerさんがコメントを作成しました:
Hey Friends,
Audit Log Product guy here – I didn't realize we didn't have these changes. Let me talk to the team taking care of the dynamic content side of things and see if we can get something going.
No ETA or commitments here, but definitely glad to cheerlead.
and thank you all for the input! It's extremely helpful in terms of uncovering “misses” and prioritizing things… Keep them coming!
コメントを表示 · 投稿日時:2024年7月22日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Is there a way to schedule the audit log to send to email via CSV/EXL? We'd like to be able to schedule the audit log to send a log of the past x day/weeks/months.
Scheduling with filtering so it alerts based on concering changes would be beneficial.
At the moment we do not have any sort of scheduling or alerting of any kind in product for Audit logs. We generally advise to export to your data warehouse or tooling which can alert and action from the API itself
However, that doesn't really help in terms of ease of use or general needs when you don't have that, or need a user friendly option, and I can definitely see how both of those could be useful.
Hannah Lucid – For the export for the csv/file, what do you use to review that from there? Do you upload the file to your analytics tool or some application to read that or are you just reviewing the file directly? Is the CSV/XML export out of convienance or is that the ideal output?
I'm curious on the full journey here, for sure
@monica — For alerting – What is your ideal outcome? Email? Webhook (3rd party integration alert) or something else? Curious to know your thoughts here — Is there anything specific or higher priority to alert on than anything else? What would you denote as a concerning change?
Thanks, both of you, for the feedback and thoughts!
コメントを表示 · 編集日時:2024年7月11日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Is there a way to exclude specific actors from the log? I'd like to remove an API actor, as well as an admin from the audit log so that I can identify users who may mistakenly make changes and look at education them.
Thank you as always :)
Hey Matt! No exclusions possible at the moment, but I have that logged as a proper feature request, and definitely see the need.
No ETA or priority on that at the moment, but I can say that explicit feedback like yours helps a lot with prioritization, so keep them coming! We're listenting :)
コメントを表示 · 投稿日時:2024年7月11日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Hey Sydney and Hannah,
Thanks so much for the in depth feedback.
My team (the Audit log and Access Log team) does not presently have these events slated to add, but I will explicitly reach out to the people who own skills and skill based routing to see if we can at least get this in the back log.
It is my intention to have a fully comprehensive (and complete) audit log service, so every event is very important.
If you have any feedback or additional thoughts on this, or more context in terms of urgency, or impact that NOT having this or anything within Audit logs or Access logs is taking, I'd love to hear it!
コメントを表示 · 投稿日時:2024年7月10日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント
Ryan Winklerさんがコメントを作成しました:
Hey Michelle, to confirm, are we talking about SSL certificates on brands & CNAME for host mapping or the SPF/DKIM/DMARC/CNAME verification for support addresses?
Just want to verify before I go into solutions or recording the right feedback.
コメントを表示 · 投稿日時:2024年7月10日 · Ryan Winkler
0
フォロワー
0
投票
0
コメント